Repository navigation
spec(automation): land browser-tab-strip v2, owner-studio v1, token-wallet v1 from 999-multibots-telegraf - #7477
Merged
Merged
Conversation
…allet v1 from 999-multibots-telegraf The three specs existed only as vendored copies in gHashTag/999-multibots-telegraf (apps/vibee-editor/render/src/spec/ and packages/vibee-atoms/src/spec/), so 999's check-t27-specs --t27 failed t27-same for each (999#3828). They are copied byte for byte from 999 origin/main to the paths their own headers name, with seals. test-report --verbose (judged by the table): - browser-tab-strip: 10 tests, 10 pass, FAIL 0, 0 vacuous - owner-studio: 2 tests, 2 pass, FAIL 0, 0 vacuous - token-wallet: 6 tests, 6 pass, FAIL 0; "the warnings come at seven, three and one day left" counts 0 runtime asserts (const-folded), but setting WARN_DAYS_FIRST=2 turns it red, so it discriminates. Negative controls in scratch copies: POLL_MS 3000->2999, STUDIO_COUNT 3->4, MARKUP_PCT 200->199 each gave FAIL 1. Census re-bless in this commit: quiet "named a path but not quiet" 181->182 and shell "run: steps" 301->302 (runner-named 280->281). Neither is moved by this change; master drifted with #7399's new workflow step and the pre-commit gate refuses any commit until the ledger matches. #7454 carries the identical bless. Closes #7463 Closes #7464 Closes #7465 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 7, 2026
Closed
Owner
Author
|
Reviewer bee: reviewed at head 6f260aa. Verdict: ready to merge once the required checks pass. No defects found. What I checked, myself:
|
This was referenced Oct 7, 2026
Closed
gHashTag
enabled auto-merge (squash)
October 7, 2026 11:43
This was referenced Oct 7, 2026
Merged
corpus: judge 26 new type conflicts from the port batches; types ledger 84 -> 110 (Refs #5906)
#7482
Merged
Contributor
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
1 participant
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.
What
Three specs added to t27, each copied byte for byte from
gHashTag/999-multibots-telegraforigin/main to the path its own header names, plus seals:specs/automation/browser-tab-strip.t27apps/vibee-editor/render/src/spec/browser-tab-strip.t2787637d875682bf2bspecs/automation/owner-studio.t27apps/vibee-editor/render/src/spec/owner-studio.t27c7959e751de2103bspecs/automation/token-wallet.t27apps/vibee-editor/packages/vibee-atoms/src/spec/token-wallet.t27425a06b53a925017Why
These existed only as vendored copies in 999; the t27 paths returned 404 and had no history. So 999's
node scripts/check-t27-specs.mjs --t27 <fresh t27>failedt27-samefor all three (999#3828). The host copy is the newer side, so it lands here unchanged. No spec was edited for t27, because byte identity is the whole point.Evidence
t27c test-report --verbose(t27c built from master 848490e), read from the table:WARN_DAYS_FIRST = 2turns it red.t27c validate-vacuityover the three: 18 tests, 0assert truebodies.Negative controls, one per spec, in scratch copies outside the tree:
POLL_MS 3000 -> 2999: FAIL 1 ("the strip is read every three seconds and fits a finger")STUDIO_COUNT 3 -> 4: FAIL 1 ("three ready studios, ...")MARKUP_PCT 200 -> 199: FAIL 1 ("an operation is sold at twice its cost, rounded up")The
seal --saveoutput for each spec is committed under.trinity/seals/automation_automation::*.json.Census re-bless (not this change's movement)
tri hooks pre-commitrefuses every commit on current master: quiet "named a path but not quiet" went 181 -> 182, and shell "run: steps" went 301 -> 302 (runner-named 280 -> 281). Both moved because #7399 added a workflow step. This PR carries the same bless as #7454, so whichever of the two merges second gets an identical hunk.A NOW entry is included in
docs/now/.Closes #7463
Closes #7464
Closes #7465
Refs gHashTag/999-multibots-telegraf#3828
🤖 Generated with Claude Code