Repository navigation
docs(skill): fill the gaps an end-to-end run hit: edge evidence, remotes, node types, evidence check - #68
Merged
Conversation
…tes, node types, evidence check
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
An agent ran the skill end to end on
0.6.1-rc.1, followingSKILL.mdas written, to diagram this repo's release flow. It validated and delivered, but had to guess in eight places. This fills them in, inskill/SKILL.mdandskill/references/authoring-contract.md:evidencefield. It now says to cite an edge on the node that makes it, or in the diagram'snotes.https://github.com/owner/repo.gitremotes are covered, not onlygit@.origin/HEAD, and gives the command for "cite only files unchanged since it".maxCharsis exact (the run saw 18 where the contract said about 17).STACKMAP_BIN: says why it's safe to rely on, next to "don't rely on variables set earlier".The evidence command passes on the test run's diagram, and exits non-zero when a cited file isn't tracked. Package tests (1,146) and site tests (114) pass.
docs, so no release on its own: it ships with the next fix or feature. The workflow example still usesqueuefor a human-run "Rollback"; it's left as is because the site catalog and the layout corpus use that example.