fix(doer): finish the fork distribution renames so releases can ship - #15
Merged
Conversation
The fork PR renamed the product but left the release pipeline red: server typecheck failed on 139 t3/* Effect service IDs (the deterministicKeys lint follows the doer-cli package name), the SSH remote runner still installed and exec'd the upstream t3 CLI, npx doer-cli had no matching bin entry, the triage playbook drifted from its source, and boot service tests still asserted the old unit name. Also switches nightlies to daily and wires NPM_TOKEN auth for the npm publish step, which had no credentials configured.
github-actions
Bot
added
vouch:trusted
Without the Blacksmith app installed, every fork workflow queued forever: CI never ran on any PR. Switch all runs-on labels to free runners (ubuntu-24.04 / windows-2025 / macos-15), drop the Blacksmith-specific apt mirror workaround, and gate deploy-relay to upstream so mirror syncs to main don't fail it. Also fix a stale package filter the rename missed: the non-server test job excluded 't3', which no longer matches anything, so doer-cli tests would have run twice (and broken the server-test isolation design). Now excludes 'doer-cli'. Timeouts raised for the slower free runners.
Both Vercel configs disabled Git deploys (upstream deploys via its release workflow instead, which is gated off on the fork), so no push would ever update doer.lagaryan.click. Enable Git integration: pushes to the production branch redeploy the site.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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. |
…oviders Built-in Claude/Codex providers default to disabled on the fork (OpenCode free is the default), so the agent-session scanner — which correctly skips disabled providers — discovered nothing and 54 tests failed. The test helper and the single importer test now pass explicit enabled flags; the disabled-instances test is untouched.
DesktopClerk bridge test still expected the t3code-dev scheme; the mobile auth exchange test still expected the T3 Code Mobile client label. Both sources were renamed in the fork PR.
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.
Follow-up to #13, which renamed the product but left the release pipeline red and parts of the install path pointing at upstream.
What was broken on
lite(verified locally, all pre-existing before this PR):deterministicKeyserrors — Effect service IDs still saidt3/...while the package is nowdoer-cli. The release quality gate runs typecheck, so no nightly or stable could ever ship.ubuntu-24.04/windows-2025/macos-15), dropped the Blacksmith apt-mirror workaround, gateddeploy-relayto upstream (it fires on everymainpush, including mirror syncs), and fixed a stale--filter '!t3'exclusion that no longer matched the renamed package.doer-clionly exposed thedoerbin, sonpx doer-cli(the exact command the CLI suggests and the download page shows) failed with 'could not determine executable'. Added thedoer-clibin alias.t3CLI (command -v t3, default spect3@latest). Now installsdoer-cli@<spec>and execsdoer.triagePrompt.tswas edited without syncing.github/triage/PLAYBOOK.md, failing the byte-identical test. Regenerated the playbook from source (also pointed atLAG-4/t3code@lite).t3code.serviceunit while the source shipsdoer.service. Updated tests, message, and user docs.click.lagaryan.doerapp id/protocols,doerCLI labels).Release pipeline changes:
publish_clinow authenticates with theNPM_TOKENrepo secret (granular npm token) — previously it had no credentials, so npm publish (and therefore every GitHub Release, which waits on it) would fail. Human step still needed: create the token, seedocs/operations/doer-distribution.md.Docs: new
docs/operations/doer-distribution.mdoperator checklist + a Distribution section inAGENTS.mdso future changes keep the fork's naming contracts (bins, schemes, artifact suffixes, service IDs, triage pair).Verification: server/ssh/contracts/desktop typechecks green; affected suites pass (cli, cloud, ssh incl. live runner tests, triage byte-identical, build-artifact 70/70 with the dev-shell env var unset). Known-red only on macOS dev shells, green on ubuntu CI: the Windows-probe test (picks up this shell's
ELECTRON_RUN_AS_NODE=1) and the entrypoint symlink test (/tmp canonicalization).release_smokealso fails repo-wide (pre-existing expo-audio patch drift, unrelated to this PR).Built with Muse Spark (opencode-go/muse-spark-1.3-contributor) via the OpenCode harness in T3 Code.