docs(readme): record Track 2 FAIL and Track 3 Wave-1 draft in the status table

[OM152002]

Closes #54. Resolves INTEGRITY-AUDIT D-04.

The root README told a reader Track 2 was "search in progress" and Track 3 was "placeholders only". Both were false — the first file anyone opens misstated the most important fact about where the project is.

Status table

Track	Before	After
Track 1	Harness in progress — no gate number yet	unchanged
Track 2	Search in progress	FAIL — no vertical locked, linking C5 DECISION + ADR-0004
Track 3	Placeholders only until Track 1 + 2 land	Wave-1 draft in docs/pitch/; all performance claims [PENDING TRACK-1]

Plus one line under the table making the dependency explicit: two consecutive vertical FAILs mean the company now rests on the Track-1 mechanism number, citing README-narrative.md §6.

Also changed

• Quick start — says what npm run ci actually runs (secret-scan → contracts → lint → typecheck → unit → integration) and that it must be green before any PR. Note it now includes test:integration, added by test: end-to-end pipeline integration test, and the compiler bug it found #70.
• Layout — adds scripts/, tests/, artifacts/, and points at architecture.md, ROADMAP.md, DEVELOPMENT.md.
• Public repo section — untouched, as the issue requires. Its secret-hygiene rules are load-bearing.
• docs/README.md "Start here" row and its open question updated; D-04 marked resolved in INTEGRITY-AUDIT, with the residual deck/objections lag explicitly left open under D-01/E-12 rather than swept in.

Verification

Check	Result
Every status claim traces to an in-repo file	yes — every cell links the artifact behind it
Counts quoted, not recomputed	2/70 and 2/75 from DECISION.md:55; 0 DURABLE from DECISION.md:72 ("Surfaces with DURABLE verdict: 0")
No performance number / percentage / gate number	scripted grep for %, Nx, tokens/latency/throughput → none
All links resolve	scripted — all 12 targets exist; verified again against the rendered page after push
npm run ci	green (37 unit + 1 integration, secret-scan clean)
npm run test:canary	green (6 tests)
npm run lint:docs	still does not exist (#53) — same substitution as PR #72

One judgment call for the reviewer

The issue says "no new metrics… no percentages". I kept the survivor counts (2 of 75, 0 DURABLE) because the issue also asks for the two-FAIL dependency line citing narrative §6, which states them, and because they are census results quoted from an accepted adjudication rather than performance claims — the same convention as the existing Week-0 line. If you read that constraint more strictly, the counts can come out and the sentence still works.