Repository navigation
docs(agents): pre-authorise expbkmain merges, and own them until deployed - #117
Merged
Merged
Conversation
…oyed Merging a green PR to expbkmain no longer needs an ask. The rule that matters is the second half: a merge is not a delivery. Nothing is verifiable until the timer has installed the artifact and expbkt3 is serving it, and a build or install can still fail after a green PR — so follow it through and report once, when the running service is on the merge SHA. bkmain is unchanged and still needs a human, because deploying it kills the team's live sessions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
Records a standing instruction from the reviewer: merging a green PR to
expbkmainneeds no further ask, but the work is not finished at merge — follow it through the build and the systemd install timer, and report only once expbkt3 is actually serving the merge SHA.The reasoning is in the diff: "merged" is not a delivery. The reviewer cannot verify anything until the new build is live, and a build or install can still fail after a green PR. Ground truth is
/home/ubuntu/.t3/expbkt3-dev/deployed-shamatching the merge commit plust3-expbkt3.serviceactive — not the PR state.bkmainis deliberately unchanged and still needs a human, because deploying it restarts the service hosting the team's live sessions.Docs only.
AGENTS.mdand every.mdpath are exempt fromcheck-fork-markers.ts, so no fork markers are needed.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.