4.1 KiB
4.1 KiB
Commitments
Track future-facing memory: promised follow-ups, unfinished loops, timed checks, and restart points.
| Date | Commitment | Trigger / Due | Owner | Status | Next Action |
|---|---|---|---|---|---|
| 2026-08-28 | Verify shared-mother-plan tid-only whole-visitor export against the current runtime ERP path. |
Explicit user authorization for ERP read access | Future authorized task | Pending authorization | Run read-only source and artifact checks without external delivery. |
| 2026-08-28 | Verify independent-order SGL/TWN and adult/child/leader headcount mappings with real ERP writes. | Explicit user authorization for controlled ERP writes | Future authorized task | Pending authorization | Use reversible values and action-specific requery evidence. |
| 2026-08-28 | Resolve AgentBus OSS attachment rejection caused by private/reserved local DNS answers. | User scheduled integration and confirmed the environment is trusted internal networking | Integration task 20260831-integrate-server-diagnostics-8b42c6d1 |
Completed in repository | Deploy/restart and run one live internal attachment verification only under separate authorization. |
| 2026-09-02 | Roll out and stage-test AgentBus account workers, account-scoped queues, administrator isolation, and owner force deletion. | Explicit authorization for database backup/migration, service restart, extension reload, account/channel configuration, staging traffic, and disposable task mutation | Future authorized rollout task | Pending authorization | Apply migrations through 023 and extension 0.5.170; verify two employee accounts/cloud PCs, unique-node exact ERP identity and mismatch, same-account worker conflict/FIFO, cross-account independence, 90-second failover, administrator task-API denial, manual/AgentBus routing, and owner-performed waiting/active force-delete cleanup. |
| 2026-09-02 | Verify the integrated native product-search execution path. | Explicit authorization for extension reload and a guarded ERP preflight/retry | Future authorized rollout task | Pending authorization | Load current extension 0.5.170, confirm the runtime handshake, then verify deterministic product selection and normal write gates without automatically retrying the earlier failed task. |
| 2026-09-03 | Bootstrap and canary the central extension-update channel. | Former rollout plan for reverted server-side EXT-001 architecture |
None while reverted | Cancelled by user rollback | Extension 0.5.170 is the current manual plugin release. Do not deploy migration 019 or the removed server updater from main; consult codex/backup-extension-update-20260903-b2e33e2 only if a future explicit decision revives the archived 0.5.167 server-update architecture. |
| 2026-09-07 | Deploy and canary team-lead task-summary notifications through AgentBus. | Former rollout plan superseded by AUTH-005 external Webhook transport | None under the active design | Cancelled by AUTH-005 | Do not configure a leader channel or send task.summary frames for summary delivery; migration 023 disables unsent legacy summary rows. |
| 2026-09-09 | Deploy and canary organization-level leader-summary Webhook delivery. | Explicit authorization for database backup/migrations through 023, protected URL/token configuration, service rollout, and one bounded external send | Future authorized rollout task | Pending authorization | Confirm the complete provider URL and real token, deploy without logging either value, observe one accepted/rejected/uncertain outcome, independently verify downstream group delivery, and never retry an uncertain attempt automatically. |
| 2026-09-09 | Validate Program-only shared-child batch creation in ERP. | Explicit authorization for migration 022 route grant, extension 0.5.170 reload, and one bounded multi-parent ERP write |
Future authorized rollout task | Pending authorization | Verify the complete target preview, then compare ordered per-parent receipts and first-non-success stop behavior without automatic retry. |
Use
Record only commitments that should affect future sessions. Routine next steps can stay in 30-worklog/current-state.md.