Current State

This file is the integrated default-branch snapshot. Feature tasks record progress in 30-worklog/tasks/{task_id}.md and propose canonical changes for the Integration Gate. Feature tasks must not rewrite this file; it changes only in integration mode.

Integrated Through

Commit 7b5d855b093af39bf834fab4f41f41b37be1170d as the inspected repository baseline.
Integration task 20260828-migrate-project-docs-6f1a9c2d for the project-documentation migration.

Current Focus

Operate the current 0.5.157 release baseline safely, keep Program/AI routing and ERP execution boundaries synchronized, and close the remaining authorization-dependent validation gaps.

Recently Completed

2026-08-28: Initialized .project-docs/, migrated durable project memory, and retired the root Planning with Files system into date-scoped history.
2026-08-28: Released Chrome extension 0.5.157, Program parser v1.0.6, input contract/DOCX 0.5.123, and five business Skills 0.5.125.
2026-08-28: Added narrow shared-mother-plan whole-visitor export using shared_plan + visitor-list + tid-only while preserving child/independent did+tid behavior.
2026-08-28: Restarted the standard 8786 control plane under authorization and observed AgentBus 4/4 channels ready across repeated samples.

In Progress

No separate repository feature task is recorded at this integration snapshot.

Next Recommended Steps

With explicit authorization, run a live read-only ERP verification of the shared-mother-plan tid-only whole-visitor export path.
With explicit authorization, perform ERP write verification for independent-order SGL/TWN and adult/child/leader headcount mappings.
Design a controlled public-DNS or host-allowlist fallback for AgentBus OSS attachments without weakening private-network SSRF blocking.

Open Questions / Blockers

Shared-mother-plan whole-visitor export has historical read evidence and static coverage but lacks a fresh authorized runtime ERP read verification.
Independent-order SGL/TWN and four headcount categories lack authorized current-version ERP write evidence.
Some AgentBus OSS attachment URLs can be rejected when local DNS resolves them to private or reserved addresses.

Risky Areas

Any ERP write, uncertain post-write state, automatic retry, or scope widening.
Passenger workbook normalization, encrypted attachment persistence, leader-contact projection, and native ERP row capacity.
Release synchronization across extension source, minimum platform version, mapping, ZIP, Skills, DOCX, and dist/release-manifest.json.

Last Updated

2026-08-28

2.6 KiB Raw Blame History