cleanup phases 6

CLAUDE.md

@@ -8,7 +8,7 @@ side of the stack lives in that project's own `CLAUDE.md`.
 > Working in `server/`? Read [server/CLAUDE.md](server/CLAUDE.md).
 > You almost never need both. A frontend change does not touch server files, and vice-versa.
 
-> Last verified: 2026-07-30 against commit `d3ec723`.
+> Last verified: 2026-08-02 against commit `e2db973`.
 
 ---
 
@@ -52,7 +52,7 @@ package, or solution — each project is built, linted, and run on its own.
 | [`server/`](server/) | Backend API | ASP.NET Core (.NET 10) · Clean Architecture · CQRS · EF Core | [server/CLAUDE.md](server/CLAUDE.md) |
 | [`product/`](product/index.md) | **Business truth** — what to build and why | Markdown (+ generated HTML) | the table above |
 | [`docs/`](docs/README.md) | **Engineering truth** — rules, the client↔server contract, flows, status, roadmap | Markdown | [docs/README.md](docs/README.md) |
-| [`dev/`](dev/README.md) | The finished build-plan chain. **History, not a project** — nothing to build in it | Markdown | [dev/README.md](dev/README.md) |
+| [`archive/`](archive/README.md) | The executed build-chain (was `dev/`) and the cleanup plan that produced `docs/`. **History, not instruction** — nothing to build from it | Markdown | [archive/README.md](archive/README.md) |
 | [`telegram-otp-bot/`](telegram-otp-bot/) | OTP relay (standalone, the pre-launch demo rail) | Node 18+, zero deps | [telegram-otp-bot/README.md](telegram-otp-bot/README.md) |
 | [`deploy/`](deploy/) | Reverse-proxy config | Caddyfile | [DEPLOY.md](DEPLOY.md) |
 | [`.githooks/`](.githooks/README.md) | Repo-managed git hooks (the pre-commit secret scan) | shell | [docs/rules/shared/git-and-gates.md](docs/rules/shared/git-and-gates.md) |
@@ -68,9 +68,8 @@ The two projects communicate over **HTTP/JSON** (optionally gRPC). The client re
 network, serving `balinyaar.ir` (client) and `api.balinyaar.ir` (server). The database is **not**
 containerised; it is a remote SQL Server. Full runbook: [DEPLOY.md](DEPLOY.md).
 
-`archive/` does not exist yet. When it does, it will hold `dev/`'s history — and the rule will be that
-**anything in it is a record, not an instruction**, because it is written in the imperative from having once
-been a prompt.
+`archive/` holds `dev/`'s history now that the clarify chain has run. **Anything in it is a record, not
+an instruction** — it is written in the imperative from having once been a prompt.
 
 ---
 

archive/README.md

@@ -0,0 +1,44 @@
+# Archive
+
+> **This folder is a historical record of how Balinyaar was built. It is not instruction.**
+> Nothing here describes current behaviour, current rules, or current plans. Do not follow a
+> procedure from this folder. Current truth lives in [`docs/`](../docs/README.md) and
+> [`product/`](../product/index.md).
+
+Everything here was written in the imperative, as a prompt for an agent to execute. The work described
+was executed weeks ago; the code has moved on since. Reading a file in this tree as if it were a
+live instruction is the exact failure mode this archive exists to prevent.
+
+---
+
+## What's here
+
+| Folder | Was | Date range | Superseded by |
+| --- | --- | --- | --- |
+| `build-chain/phases/` | `dev/phases/` — 32 executed build prompts (backend 0–15, frontend 0–15) plus `_shared/` conventions | 2026-06-28 (single day, all executed) | [`docs/rules/`](../docs/rules/index.md) (conventions), [`docs/flows/`](../docs/flows/index.md) (§7 "How to test" sections), [`docs/status/decisions.md`](../docs/status/decisions.md) (§5 "Critical rules") |
+| `build-chain/working-context/` | `dev/shared-working-context/` — per-phase STATUS files, 50 handoff/report files, the frontend request ledger, the mocks registry | 2026-06-28 → 2026-07-20 | [`docs/status/decisions.md`](../docs/status/decisions.md), [`docs/status/implemented.md`](../docs/status/implemented.md), [`docs/status/backlog.md`](../docs/status/backlog.md) (67 REQs → `BL-###`) |
+| `build-chain/contracts/` | `dev/contracts/` — the original hand-written API contract layer + the frozen 2026-07-13 OpenAPI snapshot | 2026-06-28 → 2026-07-13 | [`docs/integration/`](../docs/integration/index.md) (refreshed against 2026-07-29 code, domain-by-domain) |
+| `post-phase/` | `dev/post-phase/` — hardening (18 items), refinement (10 phases), server follow-up plans, and the 15-phase UI overhaul (plans + design audits) | 2026-07-10 → 2026-07-28 | [`docs/status/backlog.md`](../docs/status/backlog.md) (hardening + server items, re-verified against code, not trusted from checkboxes), [`docs/status/decisions.md`](../docs/status/decisions.md) (refinement decisions), [`docs/flows/testing-setup.md`](../docs/flows/testing-setup.md) (RUNBOOK.md, manual-testing-plan.md), the `frontend-designer` skill (UI design reality) |
+| `manual-testing/` | `dev/manual-testing/` — two iterations of human testing notes + screenshots (the only visual record of the pre-overhaul UI) | 2026-07-27 | [`docs/status/backlog.md`](../docs/status/backlog.md) (unfinished items); screenshots are kept as-is, unlinked from any live doc |
+| `clarify-chain/` | `docs/_plan/` — the plan that produced this cleanup: inventory, contradiction log, and the eight phase files (including this move) | 2026-07-29 → 2026-08-02 | [`docs/README.md`](../docs/README.md) records when it ran; its content is itself now history |
+
+`dev/README.md`'s own context (why this history exists at all — the derivation from an open-source
+starter, the phase-chain-then-post-phase-then-UI-overhaul shape) is folded into this file rather than
+kept as a separate leaf.
+
+## Known-stale content preserved as-is
+
+A few contradictions between this archive and current reality were found and resolved by the chain
+that produced it, recorded in full in `clarify-chain/open-contradictions.md`. Two are worth flagging
+here because they sit in files a reader might otherwise trust:
+
+- `post-phase/manual-testing-plan.md` and some of `post-phase/refinement/RUNBOOK.md` still instruct
+  `dotnet user-secrets` — removed from the codebase in `5885280`. Config lives in `appsettings.*.json`
+  and `.env.*` files; see [`docs/README.md`](../docs/README.md#configuration).
+- `post-phase/hardening/issues.md` shows 18 of 18 items unticked as of 2026-07-17, but four later
+  work chains ran without updating it. The real state is in
+  [`docs/status/backlog.md`](../docs/status/backlog.md), re-verified against code.
+
+## `product/` is untouched
+
+Nothing under `product/` moved. It was, and remains, business truth, not build history.