Repository navigation
memory: recover stale Wiki and project construction plans - #3291
Hillary Mutisya (hillary-mutisya) merged 2 commits into
Conversation
Retain useful construction work across unrelated page and maintenance-progress changes. Revalidate consulted pages, relationships and exact source access before admission, and defer genuine dependency conflicts with durable bounded recovery instead of terminal rejection. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use the confirmed service forget API rather than purging the store behind a live service. This serializes the privacy rewrite with background segment collection and preserves fail-closed quarantine checks. Verify source and separated-child deletion after closing and reopening the service. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Fixed the failing Windows Node 24 test in 04ad59b. The separation lifecycle test directly purged Validation on the pushed tree:
CI status after the bounded observation window on the pushed head:
No review threads are outstanding; human review is still required. Monitoring has ended. The PR is not being declared fully CI-green or merged. |
Summary
Motivation
An unrelated page addition or revision currently invalidates a prepared informational construction plan because the guard compares the entire family and every View revision. Useful prepared work should survive unrelated maintenance. Actual target, coverage/canonical, separation, source-revision and construction-authorization changes must still prevent stale admission or overwrites.
Behavior and compatibility
The optional persisted
planningConflictstate is additive; no migration is required. Existing automatic-pass and candidate-read budgets remain in force. Choice-only Luna, evidence-grounded maintenance, admission/editorial policy and publication authority are unchanged. This PR does not introduce native Decision1, arbitration, Inbox or partial-retention policies.Reviewer guide
Validation
Local Windows validation at
775c6a6d4354cb4fee373e835ef5279522b1bac6, based on79205019103b2f18e9b7388ad7b57d699ae4a9f1:pnpm run buildfromtspnpm exec prettier --checkon all seven changed filespnpm run code-lint -- --ratchet --base origin/mainpnpm run code-complexity -- --ratchet --base origin/main --cyclomatic 25 --cognitive 30 --new-file-cyclomatic 25 --new-file-cognitive 30pnpm run code-circular -- --ratchet --base origin/main --exceptions-file tools/scripts/code/circular-baseline-exception.jsonpnpm run code-debt -- --gate --base origin/maingit diff --checkFrom
ts/packages/memory/service:The first local circular scan lacked Git LFS in its process PATH. Rerunning with the existing portable dependency available passed, without bypassing hooks or changing the gate.
Fixtures and synthesis are deterministic/offline. No live model or whole-pipeline latency/quality qualification is claimed. CI results are separate from local validation.
Risks and rollback
Freshness now depends on complete dependency capture rather than a blanket global hash. The regression matrix covers selected and no-build paths; existing output/publication validation remains a separate guard. Repeated genuine churn intentionally pauses automatic retries after the bound and requires explicit maintenance or a new source-index generation.
Rollback is a revert of this policy change. No automatic publication, model change or data deletion is introduced.