Add chapters for session 981433083 (Haiku)

chapters/981433083.json

@@ -0,0 +1,17 @@
+[
+  {"timestamp": "0:07", "title": "Creating Accounts via REST API Subscriptions", "summary": "Subscription directories are created when users first log in or when files are pushed/pulled. Manual filesystem operations should be avoided. Publish to account operations automatically create target folders unless explicitly disabled."},
+  {"timestamp": "4:42", "title": "External Scripts for File Validation and Quarantine", "summary": "External scripts (Bash/Python) can perform sanity checks on outbound files with yes/no decision logic. Return codes (0=success, non-zero=failure) control routing. Failed files can be discarded by deletion from sandbox or routed conditionally. Process-only-result-from-preceding-step checkbox prevents empty file processing."},
+  {"timestamp": "7:12", "title": "Sandbox Lifecycle and File Handling in Routes", "summary": "Sandboxes are destroyed immediately after route completion. Files can be deleted within scripts to prevent downstream processing. Step-level condition checks based on preceding step exit status prevent processing of bad files."},
+  {"timestamp": "9:54", "title": "File Movement in Scripts vs Routing Steps", "summary": "File movement via scripts adds invisible overhead and performance cost. Recommended: use routing steps (publish to account, send to server) with conditional success/failure branches for transparency, auditability, and reporting."},
+  {"timestamp": "14:02", "title": "Ad Hoc File Transfer with Account Templates", "summary": "Ad hoc file sharing uses account templates with LDAP authentication. Rotating pool of 5 templates is acceptable. File-sharing ad hoc creates dynamic links to centralized base folder; ad hoc mailbox and package folder settings apply only to message-based ad hoc, not file sharing."},
+  {"timestamp": "16:42", "title": "Ad Hoc Base Folder and Link Architecture", "summary": "Ad hoc files store in centralized base folder with user-specific links created on-the-fly. Unlike regular subscriptions where files go into user folders, ad hoc provides single package with multiple access points. Package folder settings irrelevant for file-sharing use case."},
+  {"timestamp": "21:17", "title": "Protocol Batch Size Error and Database Tuning", "summary": "Batch size default 100 controls protocol command writes. Increase to 150 if error occurs daily on standard cluster; enterprise clusters tolerate higher values. Batch-size tuning affects database write performance under load."},
+  {"timestamp": "23:40", "title": "File Retention Period Integer Validation Error", "summary": "Misconfiguration warning in file maintenance application: retention period must be integer. Check server configuration and account-level overrides for typos, commas, or dots. Error does not prevent operation (defaults to no cleanup with -1)."},
+  {"timestamp": "28:47", "title": "Storage Quota Limitations and Monitoring Alternatives", "summary": "No built-in folder size limit exists due to multithreaded architecture. Feature under consideration for future release. Alternative: OS-level monitoring or Sentinel correlation rules with alerts at thresholds, followed by account disable if quota exceeded."},
+  {"timestamp": "31:37", "title": "Transfer Log Partitioning and Maintenance Schedule", "summary": "Partition days to prebuild creates daily partitions for transfer log retention. Always run maintenance daily as recommended. Non-daily schedules affect partition-dropping behavior differently than daily runs."},
+  {"timestamp": "36:40", "title": "Folder Access Restriction via ACLs and File Restrictions", "summary": "No UI control to hide folders from directory listings; authorization plugin required for custom visibility. Use access file directory restriction (DENY) to prevent upload/download/open. SSH clients ignore hidden dot-prefix folders by default for less-technical users."},
+  {"timestamp": "39:35", "title": "Subscription Upload Restriction Placement and Strategy", "summary": "Restrict uploads to specific folders rather than entire filesystem access when possible. Upload restrictions are cleaner than directory access denial which returns access-denied errors to users. Combine restrictions with dot-prefix naming convention for dual visibility control."},
+  {"timestamp": "43:01", "title": "Pull Failure Notifications via Conditional Routing", "summary": "Configure notifications for pull connection failures in subscription advanced routing. Separate success/failure routes with conditional triggers: pull with transfer status failure. Create new routing package route triggered on failure, add mail notification step, reorder with first-matching policy."},
+  {"timestamp": "46:09", "title": "Pull Empty File Handling and Post-Download Notifications", "summary": "Uncheck 'no files found sends to routing' when empty pulls are expected. Use 'on failure' checkbox to trigger routing only on connection failures. Post-download notifications fire when users download files, useful for publish-to-account acknowledgment workflows."},
+  {"timestamp": "50:32", "title": "Route Ordering and Conditional Triggering Best Practices", "summary": "Use conditional route expressions (transfer status = success/failure) instead of step-level proceed settings. First-matching policy prevents error-path processing on positive routes. Conditional logic at route level provides transparency, auditability, and reporting visibility vs invisible script-level file moves."}
+]