docs: record the direct-coverage wave in the audit delivery log - #568

Summary

• Doc-only. Adds section 5.2 to docs/audits/AUDIT_2026-06-10.md recording the direct-coverage wave so the audit's delivery log stays the single record of what the roadmap produced.

What Changed

• New §5.2 narrative + thirty-row table: seventeen direct test suites (test: cover login-oauth account selection and cancellation predicates #559, test: cover login-menu manage actions and prompt fallbacks #560, test: cover runAuthLogin transports, org threading, and cap handling #561, test: cover login-menu data layer targeting, view model, and drift sync #563, test: cover persistAndSyncSelectedAccount switching contract #564, test: cover runHealthCheck quick and live probe paths #565, test: cover forecast-report-shared patch persistence and save retry #566, test: cover the settings write queue retry and serialization contract #567, test: cover dashboard settings clone defaults and equality semantics #569, test: cover chooseAccount selection tiers and cursor discipline #570, test: cover ensureFreshAccessToken refresh, cooldown, and dedup paths #571, test: cover rotation proxy state init and stale-state recovery #572, test: cover the auth menu view-model formatting helpers #573 plus the later test: direct suite for the extracted account rate-limit helpers #580, test: direct suite for usage-ledger redaction and row normalization #582, test: direct suite for the settings preview builders #583, test: direct suite for settings-hub shared merge/persist helpers #584), the two fast-check property companions (test: property-check the unsupported-model fallback invariants #574, test: property-check write-queue serialization and clamp invariants #575), and eleven follow-ups from the same wave — the L3 convention doc (docs: document the class vs module-state convention (audit L3) #576), the beta.2 version-drift fix found by the baseline canary (fix: sync plugin manifest and docs portal to v2.3.0-beta.2 #577), the dead-code sweep that was closed and folded into the pre-existing refactor(lib): delete seven orphaned modules (852 dead lines) #554 (refactor: remove five orphaned modules (768 LOC of dead code) #578), the dedup-idempotence fix found by a new identity property suite (fix: deduplicateAccounts fixpoint loop and identity property tests #579), the unused-devDependency removal (chore: drop unused @fast-check/vitest devDependency #581), the closing batch of the §4.2 retry consolidation (refactor: migrate the last two hand-rolled retry loops to withRetry #585), the two §4.3 typed-error slices (refactor: throw CodexValidationError from rotation-proxy startup guards #586, refactor: abort unreadable config saves with a typed StorageError #587), the knowledge-base refreshes (docs: refresh test knowledge-base counts and list the new suites #588 for test/, docs: refresh the lib knowledge-base tree for the extraction era #589 for lib/), and the storage-suite spy-cascade isolation fix (test: stop leaked-spy cascades across the whole test runner #590).
• Updates M7's and M11's status cells in the §2 findings table now that §4.2 and §4.3 are fully executed.
• The prose notes why the numbering skips Decide whether to pin knip as a devDependency and wire it into CI #558 and IGNORE: testing MCP auth #562 (both are issues, not PRs) and docs: record the direct-coverage wave in the audit delivery log #568 (this delivery-log PR itself), and cites the two bugs the coverage method surfaced earlier in the cycle (fix(runtime): reject array helper-status files; dedupe isRecord #544 isRecord, fix(request): stream-stall failover, private-header prefix block, pinned-index message #546 stream-stall).

Validation

• npm run lint
• npm run typecheck
• npm test -- test/documentation.test.ts
• npm test / npm run build — not run for this markdown-only change; no code paths touched

Docs and Governance Checklist

• No user-visible behavior changed; audit-history doc only (additive snapshot note per docs/DOCUMENTATION.md audit policy)

Risk and Rollback

• Risk level: minimal — additive markdown in an audit history file; no code, tests, or config touched. Worst case is an adjacent-line merge conflict with the delivery-log edits on the still-open chore: add a tuned knip config and drop the unused @fast-check/vitest #555-line branches.
• Rollback plan: revert the commits on this branch (or delete §5.2); nothing depends on the section.

Additional Notes

• The new subsection is appended after the existing §5.1 table.

https://claude.ai/code/session_01XNtnkLbBiXZxfQQYLMpucB

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

this doc-only PR appends #590 (spy-cascade isolation fix for test/storage.test.ts) to the §5.2 direct-coverage wave table and threads it into the closing prose sentence. no code, tests, or config is touched.

• adds ", and a spy-cascade isolation fix in the storage suite (test: stop leaked-spy cascades across the whole test runner #590)" to the prose paragraph and a matching table row describing the vi.restoreAllMocks() guard added to the storage suite's top-level afterEach.
• no structural changes to the existing §5.2 table or any other section; the prose skip explanation for Decide whether to pin knip as a devDependency and wire it into CI #558, IGNORE: testing MCP auth #562, and docs: record the direct-coverage wave in the audit delivery log #568 is already present and still accurate.

Confidence Score: 5/5

additive markdown in an audit history file; no code, tests, or config touched — safe to merge

the change is two hunks in a single markdown file: one sentence extension and one table row, both accurately describing an already-merged PR (#590). nothing in the rest of the repo depends on this section.

no files require special attention

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["§5.2 Direct-Coverage Wave"] --> B["Test PRs\n#559–#575, #580, #582–#584"]
    A --> C["Follow-up PRs\n#576–#579, #581, #585–#590"]
    B --> D["17 direct suites\nreal logic, effectful seams mocked"]
    B --> E["2 fast-check property\ncompanions (#574, #575)"]
    C --> F["L3 convention doc (#576)"]
    C --> G["Version-drift fix (#577)"]
    C --> H["Dead-code sweep (#578→#554)"]
    C --> I["Dedup idempotence fix (#579)"]
    C --> J["§4.2 retry consolidation (#585)"]
    C --> K["§4.3 typed-error slices (#586, #587)"]
    C --> L["KB refreshes (#588, #589)"]
    C --> M["Storage spy-cascade fix (#590) ← new"]

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["§5.2 Direct-Coverage Wave"] --> B["Test PRs\n#559–#575, #580, #582–#584"]
    A --> C["Follow-up PRs\n#576–#579, #581, #585–#590"]
    B --> D["17 direct suites\nreal logic, effectful seams mocked"]
    B --> E["2 fast-check property\ncompanions (#574, #575)"]
    C --> F["L3 convention doc (#576)"]
    C --> G["Version-drift fix (#577)"]
    C --> H["Dead-code sweep (#578→#554)"]
    C --> I["Dedup idempotence fix (#579)"]
    C --> J["§4.2 retry consolidation (#585)"]
    C --> K["§4.3 typed-error slices (#586, #587)"]
    C --> L["KB refreshes (#588, #589)"]
    C --> M["Storage spy-cascade fix (#590) ← new"]

_{Reviews (22): Last reviewed commit: "Merge branch 'main' into claude/audit-49..." | Re-trigger Greptile}