Repository navigation
Name a stubbed event in the first run - #29
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From the next First Draft deploy, a State Machine whose event has effects the Compiler cannot generate stays in AASM. That event's bang form, plain form, and
may_predicate raiseNotImplementedErroruntil it is written, its State Machine examples fail through the stub, and the generated README's Behavior to write lists it. Before, such a machine kept only storage. The generatedAGENTS.mdnow says:This mirrors firstdraft/drawing-board#88 in
workshop-kit/scripts/linux/app-instructions.md: the first bullet of Setup and specs now says "A stubbed scope or event raises", so the notes name each kind of stub the generatedAGENTS.mdnames. Its clause that a Chrome that cannot start is a gap in the laptop's setup, not a First Draft defect, stays. Nothing else in the file changed. Before the deploy no README lists an event, so the rule holds on both sides of it.Verified. The wording follows the
AGENTS.mdtemplate at servicemaine2318b81. That commit's transition stubs smoke passed: its compiled README listed four stubbed Ticket events under Behavior to write, and the generated suite failed only through those stubs' State Machine examples (96 examples, 16 failures).Not run: a laptop (WSL or Mac), and Claude reading the notes. This repository has no CI.
Not for merging until the owner approves: merging changes what newly set-up laptops get.
Docs: updated
workshop-kit/scripts/linux/app-instructions.md(Setup and specs).Review: Codex (codex-review 0.8.0, max effort), session 2bb52beb-d874-4754-a759-7d3293fde3e8, approve.