The agent layer, in the shape an npm package needs - #49
Merged
Conversation
The family's delivery-cycle RFC says the sequence is shared and the hook is adapted per audience, not copied. Both halves matter here, because the .NET shape would have been wrong in two ways: it builds a solution this repository does not have, and it asks specdrift about a manifest that does not exist. So cycle.md is the shared text — byte-identical to the one goldpath ships, which is why its sixth step was made stack-neutral first: it named spec_validate and specs/, and an npm library was the repository that proved the wording was too narrow. The hook runs what is fast and what actually breaks here: the typecheck, because a red surface breaks every console in the family at once; G2, because an export with no home in the gallery docs map is a broken contract rather than a missing nicety; and G6, because an unpinned dependency is the one people breach by accident. G3, G4 and G5 need a browser or a full run and stay in CI, where they belong. The templates' post-edit formatter is dropped — there is no dotnet format here. ui-change says what each of the nine steps means for a package every console depends on: proving a test means breaking the component and watching the visual baseline go red, because a snapshot that passes with the component removed is a screenshot rather than a test; the layer that can fail is Playwright for anything about layout, dark mode or RTL, since jsdom has no layout and will pass a component that is unreadable; and the changeset is written for the consumer who must decide whether to act, not for the log. No source is touched. Typecheck clean; the hook exits 0 on a clean tree. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
The family's delivery-cycle RFC says the sequence is shared and the hook is adapted per audience, not copied. Both halves matter here: the .NET shape builds a solution this repository does not have and asks
specdriftabout a manifest that does not exist.cycle.mdis the shared text, byte-identical to the one goldpath ships — which is why its sixth step was made stack-neutral first (goldpath#252). It namedspec_validateandspecs/, and an npm library is the repository that proved the wording was too narrow.The hook runs what is fast and what actually breaks here
gallery/docs-map.jsonis a broken contract, not a missing nicetyG3 (axe), G4 (visual) and G5 (coverage) need a browser or a full run and stay in CI. The templates' post-edit formatter is dropped; there is no
dotnet formathere.ui-changesays what each step means for a package everything depends onNo source is touched. Typecheck clean; the hook exits 0 on a clean tree.
🤖 Generated with Claude Code