4 Commits

Include renames

Author	SHA1	Message	Date
weichenandCursor	aef689f9e7	Note identity migration is v27 after login_keys took v26 ... Why: Backend #170 rebased; design doc still said v26. Evidence: local unittest identity+backup OK after task-sync. Impact: docs/recovery/u1-identity-manifest.md §5.2 version note. Refs: Backend PR #170; Dev PR #426 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 05:07:25 +00:00
weichenandCursor	feccf26b90	Wire U1 I3 DB identity into svc start and tests ... Why: after #415 file markers, startup must also bind manifest.instance_id to agent_system_identity (I4). Evidence: python3 -m unittest tests.test_svc_identity tests.test_svc_recover (OK, 1 skipped NOT_RUN for real PG); Backend pin b92eaca (PR #170). Impact: svc ensure/verify + AGENT_SYSTEM_* env; stub identity; I3 SQLite tests; design doc status; modules/backend gitlink. Refs: docs/recovery/u1-identity-manifest.md §5.2; Backend #170 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 03:52:48 +00:00
weichen	c170939bb7	Implement the U1 identity manifest layer with startup verification and tests ... Why: approved design (2026-10-12) - persistent manifest becomes the startup authority, closing the param-rebuild drift, non-atomic per-key writes, and missing-config-creates-empty-system recovery gaps (plan r2 U1 / KTD1-KTD2). Evidence: SELF - python3 tests/test_svc_identity.py 21 tests OK (1 skip = real-PG identity NOT_RUN by design); make test-governance 169 OK incl. existing svc db-binding and autorecover suites; receipts appended via make evidence. Impact: scripts/svc.sh gains manifest-aware set/del/record_state/autostart plus lock-held migrate, pre-launch identity verify and an init action; new scripts/svc_manifest.py (atomic temp-fsync-rename, identity anchors, derived svc.env); unmigrated instances keep the exact legacy path (regressions green). Refs: docs/recovery/u1-identity-manifest.md; plan r2 section 7 U1	2026-10-12 02:50:32 +00:00
weichen	c43ccd7481	Draft the U1 identity manifest contract, data ownership inventory and card ... Why: U1 starts per the approved recovery plan r2 - a reviewed design contract must exist before touching scripts/svc.sh, and R3 needs an enumerable data-ownership baseline. Evidence: SELF - doc-check receipt via make evidence. First run FAILED (exit 1: proposal r2 not present in this worktree because it sits unmerged on feature/service-restart-recovery-plan); references reworded to cite the path with a pending-merge note and the check re-run PASS (exit 0). Both receipts are in the card; grounding facts verified at baseline 89174a0. Impact: docs/recovery/ additions and task card only; no behavior change; implementation gated on design review. Refs: modules/documents/docs/proposals/2026-10-12-service-restart-data-recovery.md r2 U1	2026-10-12 01:39:20 +00:00