REQ-CONFIG-003: fix authoritative ledger ISSUE provenance after #304 merge #307

Goal

Repair the authoritative docs/spec/implementation_status.csv row for REQ-CONFIG-003 so its structured provenance matches the merged repair that completed the requirement.

Evidence

PR #304 merged as d978651a0d973940e6dc7d01e8038ae5ea2c1ac9 and promoted REQ-CONFIG-003 to IMPLEMENTED based on the completing extraction-coupling repair in Issue #299 / PR #300 / merge 91507ac339b1fed65a8d0970941e8fc74eacc87c.

The PR body explicitly states acceptance criterion 2: the row must record Issue #299, PR #300, merge 91507ac....

However, the merged authoritative CSV row is currently:

REQ-CONFIG-003,IMPLEMENTED,167,300,91507ac339b1fed65a8d0970941e8fc74eacc87c,...

So PR and MERGE_COMMIT point to the completing repair, while structured ISSUE still points to historical Issue #167. The free-text EVIDENCE correctly names Issue #299, which makes the row internally inconsistent.

The same stale #167 appears in the generated docs/spec/IMPLEMENTATION_STATUS.md because it is rendered from the ledger.

Scope

Make the smallest provenance-only correction:

1. Change REQ-CONFIG-003.ISSUE from 167 to 299 in docs/spec/implementation_status.csv.
2. Preserve earlier implementation/repair history in EVIDENCE; do not erase PRs Implement ScenarioDefinition seed and GoodDefinition shapes (REQ-CONFIG-003) #79/Implement RecipeDefinition schema for REQ-CONFIG-003a #156/Implement buildInitialWorld() 17-step initialization (REQ-CONFIG-003) #163/REQ-CONFIG-003: Implement baseline scenario and complete seed types #173/REQ-CONFIG-003 debt repair: MarketId validation and RecipeDefinition bounds #288 or Issue REQ-CONFIG-003 debt: LocalMarket carries its allocated MarketId, and RecipeDefinition bounds are validated #200 references there.
3. Regenerate docs/spec/IMPLEMENTATION_STATUS.md from the corrected authoritative CSV.
4. Run the repository's implementation-status validation/check so the CSV remains exactly six columns and the generated Markdown matches it.

Non-goals

• Do not change STATUS=IMPLEMENTED.
• Do not change PR REQ-CONFIG-003: enforce extraction resource/amount coupling in RecipeDefinition validation #300 or merge commit 91507ac... provenance.
• Do not change REQ-CONFIG-004 unless an independent defect is found.
• Do not change recipe economics, extraction semantics, configuration schema, tests, milestone ordering, or specification content.

Acceptance criteria

• REQ-CONFIG-003 has structured ISSUE=299, PR=300, MERGE_COMMIT=91507ac339b1fed65a8d0970941e8fc74eacc87c.
• Historical contributing work remains represented in EVIDENCE rather than in the single completing-issue field.
• docs/spec/IMPLEMENTATION_STATUS.md is regenerated and shows Issue REQ-CONFIG-003: enforce extraction resource/amount coupling in RecipeDefinition validation #299 for the CONFIG-003 row.
• scripts/implementation_status.py --check (or the repository's current equivalent) passes.
• The CSV parses as exactly six columns for every row.

Verification

Compare the corrected row against PR #304's own stated acceptance criterion and against merged PR #300 / Issue #299. Run the authoritative ledger parser/check and verify the generated Markdown is derived from the corrected CSV.