Repository navigation
README: consumers assertions, per-gate result.json keys, manifest fields - #25
Merged
Merged
Conversation
A documentation sweep against the gates, workflows and tags. Adds the consumers gate's assertion list (the other two gates had one), the keys each gate adds to result.json, what a manifest's expected and primaryFile do, and the view-must-be-an-object change from #23 to the untagged row. States that an all-skipped consumers run passes, as it does today (#21). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Self-review rubric, scored against commit 0b2ab4d.
Claims traced to source:
Judgment calls for a reviewer:
Phases 5 to 7: no human reviewer can be awaited in a headless dispatch, and no review comment changed anything, so the table pass above stands. Merge is judged next: This comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener). drafted by Claude on behalf of Daniel Stephenson |
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.
Summary
A Stage A documentation sweep:
README.mdwas checked against the gates, the workflows, the scenario docstrings and the tags. No code changed, and every addition describes current behaviour.control-<Name>always passes, thatcandidate-<Name>passes for a pre-existing consumer, and thatcontrolandharnessare recorded only on failure. The harness'spytestandpytest-covinstalls are also stated.result.json: the keys each gate adds were undocumented, although callers read them. A table was added under the shared shape.expectedandprimaryFiledo was added.v5takes any JSON on the last line as the view (confirmed withgit show v5:gates/save_compat.py).No tracking issue: this is a gap found during triage.
Checked with no drift found
tests.yml,consumers.ymlandsave-compat.yml; the two blocks agree in all three.result.check(...)calls, in order.run(), the suite timeouts, the manifest download,pip_install()andtimeout-minutes.git ls-treeandgit greponv1tov5.tak/fishe-2026-07-04tag exists.gates/*.py, workflow header comments, and the docstrings oftak_slots.py,tak_game_saves.py,cave_saves.pyandfishe_saves.py. The remaining scenarios' docstrings were not read in this sweep, and the claims in the README's prose about them were not traced into their code.Found but not changed
workflow_call, the "Checkout gates" step appears to check out the caller rather than this repository. That is a code question, so it was filed rather than documented. The README'sworkflow_callsentence stays until the owner decides.CLAUDE.mdis stale: the repository layout omitstests/, and the CI comment describestests/as covering declared migrations only. Editing agent-loaded config needs separate authorization, so it was left alone.git rev-parse HEADthroughrun()and share the root cause.Test plan
git diff --stat origin/main:README.mdonly, 20 insertions and 2 deletions.Gate run: UNVERIFIED, not applicable.
python3.12needed an approval the dispatch could not receive, so no gate was run. This PR changes no gate, scenario or workflow, so none of the files a gate run would validate are touched.Issues not taken this cycle
gates/common.py, which is on the do-not-auto-merge list, and it needs a real gate run that this dispatch cannot make.This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
drafted by Claude on behalf of Daniel Stephenson
🤖 Generated with Claude Code