Files

2.4 KiB

notes/ manifest

File Purpose Phase / status
README.md Rules for developer planning, ongoing notes, verification evidence and phase history DOCS-01 / active
MINIFEST.md File list and ownership; MINIFEST is the exact required filename DOCS-01 / active
DOCS-01.md This documentation-governance change: baseline, scope, plan, implementation and closure DOCS-01 / implementation complete
P05-CI-01.md Scope/roots, allowed paths, implementation and Gitea CI acceptance evidence P05-CI-01 / source complete, CI blockers open
P05-CI-02.md Auth.js narrow patch, isolated Gitea CI gate, advisory triage and exact acceptance evidence P05-CI-02 / run #83 completed; residual Docker gate blocked
P05-CI-03.md Backend-only pre-change scope, disposable CI run evidence and exact acceptance result P05-CI-03 / Run #86 SUCCESS; acceptance complete
P05-SEC-01.md Pre-change security scope, remediation, exact advisory evidence, one CI run and closure P05-SEC-01 / Run #87 completed, 2 Moderate open
P05-SEC-02.md Exact root chain, seven PNPM parent overrides, one focused Gitea CI and closure evidence P05-SEC-02 / Run #88 security PASS, build blocked; parser post-run patch unverified
P05-SEC-02-A01.md Single-run Login-only final frozen/build/unit/security acceptance, scope lock and evidence P05-SEC-02-A01 / Run #89 SUCCESS, accepted
P05-OIDC-01.md Pre-change real browser OIDC Scope Lock, provision/redirect/session/negative tests and one CI run evidence P05-OIDC-01 / Run #90 FAILED at forwarder readiness; cleanup PASS; acceptance BLOCKED
P05-OIDC-02.md Pre-change loopback-forwarder scope, pinned digest/preflight fix and one real Gitea acceptance cycle P05-OIDC-02 / Run #91: private proxy PASS; socat exit 1, OIDC BLOCKED, cleanup PASS
P05-OIDC-03.md Pre-edit scoped socat exit diagnosis, immutable Python loopback fallback and one real browser CI evidence P05-OIDC-03 / source prepared, one CI pending
CHANGELOG.md Short append-only chronological phase log and links to detailed reports DOCS-01 / active

Update this manifest whenever any direct child file or directory changes. Use actual source state; a planned file must be labeled planned, not present.