Goal
Status documents still describe the state of 2026-09-22/23 although the pilot is built. Bring them to the measured state so that nobody plans from stale information.
Acceptance criteria
Not part of this task
- ADR-0001,
docs/technical/deployment-vercel.md, AGENTS.md "Project specifics", the exceptions register (showcase work in parallel)
Test plan
| Criterion |
Check |
| docs guard |
bash scripts/doku-check.sh green |
| E2E + evals |
CI run with verify-full green (link in the PR) |
| no stale claims |
fresh review subagent compares each status line with merged PRs |
Security/Privacy affected?
No.
Goal
Status documents still describe the state of 2026-09-22/23 although the pilot is built. Bring them to the measured state so that nobody plans from stale information.
Acceptance criteria
PROJECT-START.md: statusfoundation-readyplus a dated note that the pilot scope (Epics epic: vertical slice – one request end to end #2, epic: full extraction and quality gate #17, epic: robustness and operations #18) is mergeddocs/product/roadmap.md: M0 and M1 done with the PRs as evidence; M2 "built – acceptance pending" (reference project: no real test users; state what acceptance means here)README.md: status line and a short feature overview of what actually runs today (no claims without a merged PR)docs/technical/architecture.md: the "Current state" line (not the exceptions register – that is edited in parallel)verify-full, so CI runs the Playwright smokes and the eval gate once onmain's code; failures are fixed in this PR or become issuesFluory/projekte-overviewPR feat(review): review fields beside their source, correct, approve or reject #8 (projects/requestflow.md) updated to the measured state, if the session has access to that repository; otherwise say so in the PRNot part of this task
docs/technical/deployment-vercel.md, AGENTS.md "Project specifics", the exceptions register (showcase work in parallel)Test plan
bash scripts/doku-check.shgreenverify-fullgreen (link in the PR)Security/Privacy affected?
No.