From 89b16b41dc50aa8c308ba18f83e2f8497196e207 Mon Sep 17 00:00:00 2001 From: Raghu Betina Date: Mon, 12 Oct 2026 07:56:27 -0500 Subject: [PATCH] Name a stubbed event in the first run The next First Draft deploy keeps a State Machine in AASM when one of its events has effects the Compiler cannot generate. That event's bang form, plain form, and may_ predicate raise NotImplementedError until it is written, its State Machine examples fail through the stub, and the README's Behavior to write lists it. The generated AGENTS.md now says a stubbed scope or event raises. The Setup and specs bullet says how each kind of unwritten behavior fails, and it named no event. It now says a stubbed scope or event raises NotImplementedError, 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 an event, so the rule holds on both sides of it. --- workshop-kit/scripts/linux/app-instructions.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/workshop-kit/scripts/linux/app-instructions.md b/workshop-kit/scripts/linux/app-instructions.md index 79d139d..6e9404d 100644 --- a/workshop-kit/scripts/linux/app-instructions.md +++ b/workshop-kit/scripts/linux/app-instructions.md @@ -14,11 +14,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 spec that fails through behavior the README's **Behavior to write** lists is work to do: - write that behavior until its specs pass. A stubbed scope raises `NotImplementedError`, a stubbed Policy rule - returns `false`, and a deletion outcome First Draft left out fails its spec with `RecordNotDestroyed`. Write every - item that section lists, including a denying rule no failing spec names. 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. + write that behavior until its specs pass. A stubbed scope or event raises `NotImplementedError`, a stubbed Policy + rule returns `false`, and a deletion outcome First Draft left out fails its spec with `RecordNotDestroyed`. Write + every item that section lists, including a denying rule no failing spec names. 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