docs: migrate project memory governance
This commit is contained in:
1 parent
7b5d855b09
commit
e7aa58a203
37 files changed
+942
-34
No files matched your search
@@ -0,0 +1,45 @@
|
||||
# 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
|
||||
|
||||
1. With explicit authorization, run a live read-only ERP verification of the shared-mother-plan `tid-only` whole-visitor export path.
|
||||
2. With explicit authorization, perform ERP write verification for independent-order SGL/TWN and adult/child/leader headcount mappings.
|
||||
3. 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
|
||||
@@ -0,0 +1 @@
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
# Task History
|
||||
|
||||
This is integrated history. Feature tasks write only their task-scoped records; Integration Gate updates this file when a concise milestone remains useful.
|
||||
|
||||
| Date | Milestone | Result | Detail |
|
||||
|---|---|---|---|
|
||||
| 2026-08-28 | Project documentation migration | `.project-docs/` became the sole active project-memory system; legacy root planning files were preserved in date-scoped history. | [Integration task](tasks/20260828-migrate-project-docs-6f1a9c2d.md) |
|
||||
| 2026-08-28 | AgentBus reconnect | Authorized control-plane restart completed; database, migration 014, and 4/4 channels were repeatedly ready. | [Archived legacy progress](../../archive/project-history/2026-08-28/legacy-planning-with-files-progress-final.md) |
|
||||
| 2026-08-28 | Shared mother-plan whole-visitor export | Released strict `shared_plan + visitor-list + tid-only` routing and execution boundaries in extension `0.5.157`. | [Release gate](../../agent设计规范/test-fixtures/lwlt-lifecycle/release-gate.md) |
|
||||
@@ -0,0 +1,35 @@
|
||||
# Task: {title}
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: {task_id}
|
||||
- Mode: {mode}
|
||||
- Branch: {branch}
|
||||
- Worktree: {worktree}
|
||||
- Base commit: {base_commit}
|
||||
- Owner: {owner}
|
||||
- Status: Planning
|
||||
|
||||
## Scope
|
||||
|
||||
- {scope}
|
||||
|
||||
## Intent And Constraints
|
||||
|
||||
- {intent_or_constraint}
|
||||
|
||||
## Outcome
|
||||
|
||||
- Not completed.
|
||||
|
||||
## Verification
|
||||
|
||||
- Not run.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- None recorded.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- None recorded.
|
||||
@@ -0,0 +1,69 @@
|
||||
# Task: Migrate project docs governance
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: 20260828-migrate-project-docs-6f1a9c2d
|
||||
- Mode: Integration
|
||||
- Branch: main
|
||||
- Worktree: /Users/inmanx/Documents/lwltAPI
|
||||
- Base commit: 7b5d855b093af39bf834fab4f41f41b37be1170d
|
||||
- Owner: codex
|
||||
- Status: Ready for Integration
|
||||
|
||||
## Scope
|
||||
|
||||
- Initialize and adopt `.project-docs/` as the repository's durable project-memory system.
|
||||
- Migrate known current state, architecture, domain boundaries, evidence pointers, commitments, and maintenance rules from the legacy root planning files and active project documentation.
|
||||
- Archive and retire root `task_plan.md`, `findings.md`, and `progress.md` so the repository has one active documentation system.
|
||||
- Update `AGENTS.md`, `README.md`, and repository hygiene tests to enforce the new entry and ownership workflow.
|
||||
|
||||
## Intent And Constraints
|
||||
|
||||
- Preserve all legacy content in date-scoped history before removing root files.
|
||||
- Do not fabricate unknown project facts; keep unknowns and authorization-dependent validation explicit.
|
||||
- Do not change business behavior, source contracts, release artifacts, ERP state, services, deployment, or external systems.
|
||||
- Keep this migration exclusively owned under the integration lock; no sub-agents or concurrent task scopes are involved.
|
||||
- Use the bundled `maintain-project-docs` scripts for initialization, ownership, validation, drift checking, and task completion.
|
||||
|
||||
## Plan
|
||||
|
||||
1. Scan active references and inspect governance/test files that depend on the legacy root planning files.
|
||||
2. Freeze exact legacy files into `archive/project-history/2026-08-28/` and update its index.
|
||||
3. Populate the canonical `.project-docs` brief, current state, decisions, architecture, domain, evidence, reflection, commitments, and maintenance records from verified local sources.
|
||||
4. Update project entry documents and repository hygiene checks, then remove the legacy root files.
|
||||
5. Run document checks, drift checks, the repository's five required gates, size/hash/link/diff checks, and complete the task context.
|
||||
|
||||
## Outcome
|
||||
|
||||
- Initialized the complete `.project-docs/` concurrency and canonical-memory tree with the bundled non-overwriting initializer.
|
||||
- Claimed the known dirty `main` worktree in exclusive Integration mode and acquired the repository integration lock.
|
||||
- Populated project positioning, success criteria, integrated state/history, decisions, architecture, domain rules, glossary, evidence, reflection, commitments, stale-state guidance, and project authority pointers from verified local sources.
|
||||
- Updated `AGENTS.md`, `README.md`, and repository hygiene tests so future repository tasks use `maintain-project-docs` and the Concurrent Task Gate.
|
||||
- Preserved the final legacy `task_plan.md`, `findings.md`, and `progress.md` byte-for-byte in `archive/project-history/2026-08-28/`, indexed their hashes, and removed the root copies to prevent dual project-memory systems.
|
||||
- No business code, contracts, release artifacts, ERP state, service process, deployment, or external system was changed.
|
||||
|
||||
## Verification
|
||||
|
||||
- 2026-08-30 completion recheck: the user explicitly authorized finishing, committing, and releasing the known governance migration changes.
|
||||
- `check_project_docs.py`: passed.
|
||||
- `task_context.py doctor`: registry consistent.
|
||||
- `check_doc_drift.py --task-id 20260828-migrate-project-docs-6f1a9c2d`: passed after resolving the initializer placeholder issue recorded below.
|
||||
- Repository governance: 9/9 passed, including root boundaries, `.project-docs` authority, Markdown links, archive indexes, release hashes, and package/source equality.
|
||||
- TypeScript check: passed.
|
||||
- Control-plane tests: 127/127 passed.
|
||||
- Legacy/platform/tools tests: 248/248 passed.
|
||||
- Build: passed.
|
||||
- Two macOS-generated `.DS_Store` files were moved out of the repository before the final verification; they contained no project source or task state.
|
||||
- Final legacy archive SHA-256 and byte comparisons: all three passed.
|
||||
|
||||
## Gate Notes
|
||||
|
||||
- The first drift check correctly blocked six initializer-created `.gitkeep` files inside task-owned supporting directories because they had no task ID owner. The empty placeholders were removed; task records create their parent directory automatically, and future optional supporting directories are created only when a valid task-prefixed record is needed. No project information was deleted.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- Authorization-dependent ERP and AgentBus follow-ups were integrated into `.project-docs/80-commitments/commitments.md`; this documentation migration creates no additional operational follow-up.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- None. This task ran in Integration mode and applied the user-approved project-memory migration directly to canonical documentation.
|
||||
Reference in new issue
Block a user