Skip to content

fix(tests): resync spanish-company-data's health-check input; 2026-09-18 check-in - #684

Merged
petterlindstrom79 merged 4 commits into
mainfrom
chore/checkin-2026-09-18
Sep 18, 2026
Merged

petterlindstrom79 merged 4 commits into
mainfrom
chore/checkin-2026-09-18

Conversation

@petterlindstrom79

Copy link
Copy Markdown
Member

What

Morning operating session, 2026-09-18.

  1. Startup-migration block 0116 resyncs spanish-company-data's dependency_health input from {"company_name":"Telefonica"} (correctly refused as an ambiguous registry name, so the suite never measured availability) to the manifest's {"nif":"A20072302"}. Mirrors block 0115 line for line: ledger guard, exact-stale-literal predicate, baseline cleared, one auto_fix event per affected row. Ledger row M059, added to the 13 known_overlaps entries 0115 is in, with disjointness notes. Closes the Spanish half of DQ-33 on deploy.
  2. fixtures:drift remediation text no longer says a fix needs a founder-authorised attended session (DQ-27) or that onboard.ts --backfill cannot do it; it names the deploy-time block route and warns off the direct production write.
  3. Operating record, CEO brief, DQ-33 update.

Evidence

  • Live, registered executor, 2026-09-17 and 2026-09-18: Telefonica → refused; A20072302 → CONSTRUCCIONES AMENABAR SA, active.
  • Production read-only: exactly one test_suites row holds the stale literal.
  • Tests + five mutations, all caught: archive/receipts/2026-09-18-test-run-block-0116-spanish-resync.json.
  • npm run typecheck, migrations:check, migrations:test, receipts:check, docs:check, context:check, codex:check, programs:check, CEO brief check — pass locally.

Deploy mechanism (DEC-20260504-C)

The block is in the BLOCKS array runStartupMigrations() iterates on boot (the registration-order test fails if removed). Post-deploy check: the suite's input equals the NIF and startup_migration_ledger has 0116_resyncSpanishCompanyDataDependencyHealth with rows_affected = 1.

Bulk-operation protocol (DEC-20260504-B)

One suite, already on schedule, starts passing; run frequency unchanged, no extra vendor quota. Not a resumption event.

Review

Independent review by a fresh read-only agent in a separate context (same provider, per the 2026-09-07 policy): PASS, no must-fix/should-fix. It reran the ledger check, verified every overlap claim against source, confirmed the new CLI text against onboard.ts, and caught two extra mutations of its own. Detail in the operating record, section F.

🤖 Generated with Claude Code

petterlindstrom79 and others added 4 commits September 18, 2026 08:11
…ock 0116)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…e route

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@petterlindstrom79
petterlindstrom79 merged commit bbc3a3c into main Sep 18, 2026
3 checks passed
@petterlindstrom79
petterlindstrom79 deleted the chore/checkin-2026-09-18 branch September 18, 2026 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant