Repository navigation
Use Ticket run names throughout agent-facing documentation - #1147
Merged
Merged
Conversation
This was referenced Oct 23, 2026
Merged
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
Renames the glossary, agent-facing text, manual and README together; regenerates prompts and site pages. ADR 0022 records why stored
Runkinds remain stable. Old README bookmarks and manual links still resolve.Closes #1102
Evidence
node --test --test-name-pattern='manual starts folded' site/tests/pages.test.cjsfailed looking for “What a Ticket run does”.After: the same navigation test passes at 320px without JavaScript.
cargo test prompts_page: 12 passed.cargo fmt --check: passed.scripts/affected-tests issue-1101selected the browser and full Rust suites: 45 site tests and 1,243 active unit tests passed. It stopped at a host-only systemd warning from the installedsnapd.service. With a temporary process-scoped Snapd mask, all 7site_deploytests passed; the seven remaining integration binaries then passed. Coverage reconciliation against Cargo metadata confirms all 56 integration binaries passed.tag.gpgsign=falseprevents this machine's signed-tag prompt;SYSTEMD_UNIT_PATHisolates its incompatible Snapd unit. No repository or host-service changes were made for these environment issues. Timed selector: 1,020.00s; targeted continuation: 281.09s. Incremental compilation was included; dependency compilation ran earlier.notification documentation limits suppression to child Ticket runstest now passes.Test seams
prompts_pageand site browser tests.Review coverage
Independent Standards and Spec reviews compare against
issue-1101. Each read all 25 changed files, including generated output and the final CI policy wording. Both identified the notification child-qualifier defect; their exact reproductions failed, and the correction and regression test were reviewed. Standards: 1 finding resolved. Spec: 1 finding resolved.Unread changed files: none on either axis. Generated-output exclusions: none. Full reports and each axis's final files-read list are saved in
.thirdshift-review-5b6VQm/standards.mdand.thirdshift-review-5b6VQm/spec.mdin the worktree.Unaddressed findings
Standards
None skipped; the sole finding was reproduced and fixed.
Spec
None skipped; the sole finding was reproduced and fixed.
Merge Danger
Door: two-way
Blast Radius: documentation
The change affects agent instructions, generated documentation and manual anchors. CLI output and stored kinds retain their current spelling for the next Ticket.
Built with codex · gpt-6.1-sol · high