Repository navigation
Use plain Ticket run names and five workflows on the site - #1154
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
Use Ticket run, Self-merge and plain schedule names across the homepage, How it works and Architecture. Explain up front in the homepage and README that thirdshift drives your own logged-in agents and is free and open source; name subscription usage only for Claude Code. Preserve the press drawing, colours, type, recorded replay, name story and
/videos/.Closes #1104
Evidence
node --test --test-name-pattern='homepage explains Ticket' site/tests/pages.test.cjsfailed on the old headline.After: the focused copy, five-workflow, manual-link and responsive checks passed, including 320, 390 and 1280px with JavaScript on and off.
current share cardbrowser test also failed.After: both checks pass after updating the tags on How it works and Architecture.
NODE_PATH="$PWD/site/node_modules" node docs/share-card/render.mjsand inspected it. The four recorded stderr columns and colophon story compare unchanged against the base.scripts/affected-tests origin/issue-1101selected the browser checks and full Rust suite. Locally: all 48 browser tests and 1,243 Rust unit tests passed (3 ignored). A host-onlytag.gpgSign=falsecommand override avoided an inherited signed-tag editor prompt; no Git settings were changed. Stopped the remaining local integration run once CI passed for this exact head, reusing CI asdocs/testing.mddirects.1fbc58f: fullcargo test, formatting/clippy, site and Console checks. The full Rust run includesshare_card(4 passed) andsite_deploy(7 passed). Initial local Rust compilation took 2m 17s; the successful local unit-test phase took 142.60s, excluding compilation. The redundant full local run was cancelled, so no full local wall-time result is claimed.Test seams
Review coverage
Independent Standards and Spec reviews used
origin/issue-1101at4113afbas the fixed point. Standards: 0 findings. Spec: 1 P2 finding, reproduced and fixed with a retained regression test. Both reviewers inspected all six changed files, including the PNG, and reviewed the correction. Generated-output exclusions: none. Unread changed files: none.Unaddressed findings
Standards
None.
Spec
None.
Merge Danger
Door: two-way
Static copy, SVG labels, metadata and browser tests; no runtime or stored-format changes.
Blast Radius: site
Built with codex · gpt-6.1-sol · high