DevToolsTranslator: release-readiness blockers

[notion-portfolio-actuator]

This issue is the current governed execution slice for DevToolsTranslator.

Why this issue is current

• Keep the active GitHub issue aligned with the real next slice instead of kickoff-era wording.
• Carry the project's real blockers, check posture, and evidence needs inside the governed lane.

Current focus

Clear the remaining release-readiness blockers on main: manual Chrome sign-off, Chrome Web Store credentials, and updater-signature input.

Check posture

Refreshed on 2026-05-17.

• Local readiness command for 0.1.0-beta.14 still reports status=blocked because release inputs are missing.
• Release manifests are present for the readiness check: required count 4, missing list empty.
• Commit 6a92b17 removed hardcoded pnpm/action-setup version pins so workflows use repo packageManager: pnpm@11.1.2.
• Commit adb9d89 moved release/perf workflows to Node 24 so pnpm@11.1.2 can run in GitHub Actions.
• Manual dispatch of release-extension-stage-controller on 2026-05-17 passed after the pnpm and Node workflow fixes.

Current blockers

• manual_smoke_missing: docs/PHASE6_SMOKE_EVIDENCE.md still has interactive_chrome_manual: not_run.
• cws_credentials_missing: CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN, and CWS_EXTENSION_ID are not available to the readiness check.
• updater_signature_missing: UPDATER_SIGNATURE is not available for staged public prerelease readiness.

Done when

• Manual Chrome sign-off is captured with the required pass marker.
• Required Chrome Web Store credentials and updater signature are available in the release environment.
• A fresh promotion readiness check reports ready or only intentionally accepted manual release gates.
• The active Notion page and this governed issue describe the same slice.

[notion-portfolio-actuator]

Operational execution checkpoint for DevToolsTranslator.

• Active packet focus: complete Chrome sign-off, prepare CWS credentials, and resolve the updater signature blocker.
• Current blocker: Release automation and staged rollout testing.

This comment marks the next governed execution slice for the project.

[saagpatel]

Governed execution truth refreshed on March 24, 2026.\n\n- Stage-controller automation is currently healthy.\n- The remaining workflow-side blocker is the March 21 perf/reliability failure, plus the still-manual release inputs called out in the issue body.\n- No local setup blocker needs to be reopened from this repo state.

[saagpatel]

2026-05-18 Codex checkpoint after reselecting DevToolsTranslator as the next portfolio move.

Fresh checks:

• Local repo: main...origin/main, clean.
• Promotion readiness: pnpm run release:promotion:readiness -- --version 0.1.0-beta.14 --channel staged_public_prerelease still exits blocked.
• Passing check: release_manifests_present with all 4 required manifests present.
• Remaining blockers: manual_smoke_missing, cws_credentials_missing, updater_signature_missing.
• Local env has no CWS_ or UPDATER_SIGNATURE values.
• gh secret list --repo saagpatel/DevToolsTranslator returned no repo secret names, so the CWS/updater inputs do not appear configured in repo secrets either.

I did not mark manual Chrome smoke as passed from shell automation. The next real release move is still operator-owned:

1. Run the interactive Chrome checklist and append interactive_chrome_manual: pass|date=YYYY-MM-DD|observer=<name> to docs/PHASE6_SMOKE_EVIDENCE.md.
2. Add repo secrets: CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN, CWS_EXTENSION_ID, and UPDATER_SIGNATURE.
3. Rerun promotion readiness for 0.1.0-beta.14 / staged_public_prerelease; if it returns ready, proceed to the dry-run release/promotion path before any non-dry-run publish.

[saagpatel]

2026-05-18 refresh

Current release-readiness proof is refreshed on main.

• Local repo is clean at 9a83654.
• Latest scheduled release-extension-stage-controller run on main passed.
• Latest scheduled perf-reliability-regression run on main passed.
• pnpm --filter @dtt/extension build passed.
• pnpm --filter @dtt/extension test passed.
• Dry-run manifests were regenerated for macOS, Windows, Linux, and Chrome Store public extension for 0.1.0-beta.14.
• release:extension:cws:dry-run passed for pct_5.
• release:updater-feed:dry-run passed for staged_public_prerelease.
• Promotion readiness is still correctly blocked only by: manual_smoke_missing, cws_credentials_missing, and updater_signature_missing.

No repo-code blocker was found in this pass. The next release move is operator input: capture manual Chrome smoke, add Chrome Web Store credentials, add UPDATER_SIGNATURE, then rerun promotion readiness.

[saagpatel]

2026-05-18 verification checkpoint: repo is clean on main at 9a83654. pnpm test and pnpm typecheck passed locally. pnpm release:promotion:readiness -- --version 0.1.0-beta.14 still reports blocked only on manual_smoke_missing, cws_credentials_missing, and updater_signature_missing; release manifests are present. Recent release-extension-stage-controller and perf-reliability-regression runs are green. No repo-code blocker found in this pass, so the remaining release-readiness work is manual Chrome sign-off plus release secret inputs.