Last 7 MUST gaps filled — and not fabricating a STAR to do it
Closed the final 7 MUST-level coverage gaps across three decks (concepts, phrases, dbperf). Routed the trust-battery / no-surprises gaps to phrase cards (how to articulate them) instead of inventing behavioral STAR stories. MUST coverage is now complete; only should/nice depth remains.
Finished the MUST list from the coverage audit — the last 7 gaps, spread across three different decks and shapes: three /concepts cards (domain modeling from requirements, designing a public API / method signatures, when NOT to use a fancy data structure), three /phrases cards (reasoning from first principles out loud, building trust / the trust battery, proactive no-surprises communication), and one dbperf walkthrough (serialization failures — SQLSTATE 40001 — and the retry-the-whole-transaction pattern). Generated and fact-verified, same as the earlier batches.
The honest call here was the two behavioral-flavored gaps. The audit flagged trust-battery and no-surprises under the behavioral deck, and those are the interviewer's stated hot buttons, so they matter. But the behavioral cards are built from the owner's REAL stories, and I don't have a verified anecdote for "a time you built trust" — inventing one would be exactly the kind of fabrication this project's logging rules forbid. So instead of fake STAR cards, they became /phrases cards that teach how to ARTICULATE trust-building and no-surprises communication out loud — generic phrasing grounded in the interviewer's stated value, claiming no specific personal event. If the owner wants a dedicated behavioral STAR for these, that needs a real story from him, not from me.
One integration snag: the dbperf array's last existing element had no trailing comma (fine when it was last), so appending after it produced }\n{ and a syntax error. Fixed by anchoring the insert on the closing } + ]; and adding the comma.
Status: code committed (f8ebb0e), typecheck and build clean, all 7 cards confirmed present (CONCEPTS 187->190, DBPERF 6->7, +3 phrases). The deploy itself is blocked on an expired AWS credential — InvalidClientTokenId on the ECR login — so this is live in the repo but not yet on the phone until creds are refreshed and the deploy re-runs. MUST coverage is now 47/47; what remains is should/nice depth only.