Skip to content

Build log: unique cake-name index re-raised 2026-09-07 was already shipped; re-verified, counts unchanged - #17

Merged
erikshafer merged 1 commit into
mainfrom
docs/unique-index-reverified
Sep 8, 2026
Merged

erikshafer merged 1 commit into
mainfrom
docs/unique-index-reverified

Conversation

@erikshafer

Copy link
Copy Markdown
Owner

Doc-only. The 2026-09-07 mock audience synthesis restated the skeptic review's 2026-09-04 finding that the after twin lacked a unique index on Cake.Name. That index already ships: Audit Tier 2 (b24a723, PR #5) added opts.Schema.For<Cake>().UniqueIndex(UniqueIndexType.Computed, x => x.Name) to the after twin's Program.cs, and the 2026-09-05 hardening added the shared database_refuses_duplicate_cake_name_behind_the_api scenario that goes red if either twin loses its index. Adding the statement again would register the same index twice, so no code changed.

Re-verified this session and recorded in docs/build-log.md:

  • SeedData seeds three distinct cake names.
  • The contract fixture builds the index on every fresh Testcontainers database via ApplyAllConfiguredChangesToDatabaseAsync.
  • The existing compose volume already carries after.mt_doc_cake_uidx_name (Marten's default AutoCreate.CreateOrUpdate patched the table on 2026-09-05); no down -v needed for the live demo.
  • Suite 54/54 (27 scenarios x 2) and unit tests 15/15, 0 warnings.
  • Whole-twin counts by the inventory's rule, unchanged: before 2,140 raw / 1,775 non-blank, after 703 / 581. The index and its comment have been inside the after twin's number since 2026-09-04, so the deck's scorecard keeps 703 / 581.

No change to src/, openspec/, docs/file-inventory.md, or the README.

…09-07 was already shipped; re-verified, counts unchanged
@erikshafer erikshafer self-assigned this Sep 8, 2026
@erikshafer
erikshafer merged commit 70a2b13 into main Sep 8, 2026
1 check passed
@erikshafer
erikshafer deleted the docs/unique-index-reverified branch September 8, 2026 03:18
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