Files
ZitPlane/project/CHANGELOG.md
T

2.4 KiB

ZitPlane development changelog

This is the developer-focused implementation history. notes/CHANGELOG.md is the compact planning/phase log; docs/ is for users.

Date Phase Files / behavior introduced Git / evidence
2026-11-22 P01 Initial Monorepo directories, root AGENTS/README, architecture & phase docs 8f54ccb, docs/PHASES.md
2026-11-22 P02 core/backend/zitadel/dev.py, local-only Compose with official ZITADEL/Postgres/Traefik and prebuilt Login 433a0a3 then eadd0e5; docs/P02-EVIDENCE.md. Live runtime blocked
2026-11-22 P03 auth/ui/v2/ official v4.20.4 source and matching client/proto/pnpm/Nx dependencies 4404849; docs/P03-SOURCE-IMPORT.md; no build
2026-11-22 P04 users/ui/ Account Portal OIDC, pages, styling, read-only identity API 40af500; docs/P04-ACCOUNT-PORTAL.md; no build/CI
2026-11-22 DOCS-01 Documentation governance; developer architecture, reviewed first-party function/file/page mapping and 701-path source inventory; user manual/setup/status/troubleshooting Documentation complete; manifest/link/source-scope audit PASS; notes/DOCS-01.md, local commit SHA via Git history
2026-11-22 P05-CI-01 .gitea/workflows/p05-ci.yml, tests/ci/**, Account npm lock, Login pnpm importer reconciliation and in-scope Alpine Git checkout correction Run #81 overall FAIL; 2 jobs PASS, 2 FAIL; Login 1219/1219 tests PASS, Account TS2345 and Docker checkout blocked; notes/P05-CI-01.md
2026-11-22 P05-CI-02 Type-safe Auth.js subject narrowing, Account anonymous negative tests, Login regression, structured advisory triage and CI-only portless Docker override Run #83: 3 PASS/1 FAIL; Docker proxy 8080 collision, cleanup PASS, portless fix unverified; see notes/P05-CI-02.md
2026-11-22 P05-CI-03 Dedicated manual backend-only CI acceptance, guarded disposable Compose, persistence/ready/JWKS probes and owned-state cleanup Gitea Run #86 SUCCESS on 03fb589; all steps PASS; notes/P05-CI-03.md

Required entry for each future change

Date, phase, approval/scope, baseline SHA, source files changed, reason/functional effect, interface/security impacts, migration/config steps, test/CI evidence, docs updated, commit SHA, verified/unverified limitations. Append one record for every approved change/fix, including documentation-only changes. Never overwrite old conclusions without noting correction.