From 2a6d04061fdae4d22a1a30d12d7f8dec990a63a8 Mon Sep 17 00:00:00 2001 From: Raghu Betina Date: Mon, 12 Oct 2026 03:52:02 -0500 Subject: [PATCH] Key first-run failures on Behavior to write The next First Draft deploy keeps a polymorphic Reference's storage when a target cannot carry the authored deletion outcome. Such a target refuses its own deletion while a record references it, and a cascade or nullification it leaves out fails its deletion spec with RecordNotDestroyed. The README's Behavior to write lists that outcome, and the generated AGENTS.md now calls any spec that fails through behavior on that list work to do. The app-session notes called only a NotImplementedError work to do, so an agent would have reported a left-out deletion as a First Draft defect. They now key the first run on the Behavior to write list and name both failure shapes, as the app's AGENTS.md and the Drawing Board's notes do. A Chrome that cannot start is still a gap in the laptop's setup. Before the deploy no README lists a deletion outcome, so the rule holds on both sides of it. --- workshop-kit/scripts/linux/app-instructions.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/workshop-kit/scripts/linux/app-instructions.md b/workshop-kit/scripts/linux/app-instructions.md index 82834f0..da261a6 100644 --- a/workshop-kit/scripts/linux/app-instructions.md +++ b/workshop-kit/scripts/linux/app-instructions.md @@ -13,10 +13,11 @@ except on testing, where the app's `AGENTS.md` and README govern. ## Setup and specs - After Compile, set up the app, build its assets and run its specs as its README says, before the first preview. - In that first run, a `NotImplementedError` that names behavior listed under the README's **Behavior to write** is - work to do: write that behavior until its specs pass. If Chrome itself cannot start, this laptop's setup is - missing something; any other failure in that run is a First Draft defect. Either way, tell the user which spec - failed and its error. Never edit or delete a generated spec to make it pass. + In that first run, a spec that fails through behavior the README's **Behavior to write** lists is work to do: + write that behavior until its specs pass. A stub raises `NotImplementedError`, and a deletion outcome First Draft + left out fails its spec with `RecordNotDestroyed`. If Chrome itself cannot start, this laptop's setup is missing + something; any other failure in that run is a First Draft defect. Either way, tell the user which spec failed and + its error. Never edit or delete a generated spec to make it pass. - System specs drive Chrome on this laptop directly; there is no Selenium container to start or stop. ## Web app