Repository navigation
queen-job: publish release-t27c 0.5.2 (the first release the swarm makes) #7982
Description
The swarm makes the t27c 0.5.2 release (#7965, #7966). Owner, 2026-10-09 (translated): "Yes: a rehearsal, then the release." The rehearsal was green: #7967, job #2.
The card release-t27c runs every step for real, at the master commit it pins when it starts:
- version-truth: both manifests say 0.5.2.
- tag-absent: no tag
t27c-v0.5.2and no 0.5.2 on the registry. - A GitHub release
t27c-v0.5.2. - The release workflow it fires.
- t27c 0.5.2 on crates.io.
The publish step needs TRIOS_QUEEN_RELEASE_TOKEN on the Queen's service. Until the owner sets it, the job waits at the publish step and reports BLOCKED, visibly. It fails after one day if nothing changes.
Progress: https://trios-agent-server-production.up.railway.app/queen/public-jobs
Job
card: release-t27c
version: 0.5.2
mode: publish
User Scenarios
- Given the swarm has prepared t27c version 0.5.2 and the master commit is pinned, When the release-t27c job is triggered in publish mode, Then it verifies both manifests say 0.5.2, confirms no tag
t27c-v0.5.2exists and no 0.5.2 on crates.io, creates a GitHub releaset27c-v0.5.2, fires the release workflow, and publishes t27c 0.5.2 to crates.io usingTRIOS_QUEEN_RELEASE_TOKEN, reporting BLOCKED if the token is missing and failing after one day.
Requirements
FR-001: The release-t27c job MUST verify that both version manifests report version 0.5.2.
FR-002: The job MUST check that git tag t27c-v0.5.2 does not exist and that crates.io does not have version 0.5.2 published.
FR-003: The job MUST create a GitHub release named t27c-v0.5.2 at the pinned commit.
FR-004: The job MUST trigger the release workflow (e.g., .github/workflows/release.yml) after creating the release.
FR-005: The job MUST publish t27c 0.5.2 to crates.io using TRIOS_QUEEN_RELEASE_TOKEN, and if the token is absent, MUST report BLOCKED visibly and fail after 24 hours.
Success Criteria
- The command
t27c test specs/tools/trinity/tri/swarm.t27exits with exit 0. - The command
python tools/queen/publish.py --version 0.5.2 --dry-runexits with exit 0. - The GitHub Actions workflow
.github/workflows/release.ymlruns successfully for tagt27c-v0.5.2(exit 0). - The crate t27c version 0.5.2 appears on crates.io after publish (1 crate published).
Boundary
- specs/tools/trinity/tri/swarm.t27
- specs/docs/chapters/queen.t27
- tools/queen/publish.py
- .github/workflows/release.yml
- scripts/tri_loop/swarm.py
- bootstrap/t27c.py
Activity
gHashTag commentedon Oct 9, 2026
Done. The swarm made this release end to end; no laptop step was involved after the owner's issue.
t27c0.5.2 inbootstrap/Cargo.tomlat bc441c0t27c-v0.5.2tag before the jobSwarm job #3 reports
done, step 5.Of the 92 minutes, about 90 were spent waiting for a runner in the Actions queue: 695 queued runs at the peak. The job's own steps took seconds.
The blog-share desk (gHashTag/999-multibots-telegraf#3923, spec v5 in #8084) will ask the owner in Telegram whether to post this release. That question comes after the owner answers the open question about t27b 0.1.0. Nothing is posted without the owner's yes.
gHashTag commentedon Oct 9, 2026
t27c 0.5.2 is released.
t27c-v0.5.2-> bc441c0 (git ls-remote).t27cmax_version = 0.5.2.Closing. Watched by node2 (A2A #7996).