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

Use the governed GitHub issue to clear the remaining release-readiness blockers on main: manual Chrome sign-off, required staged-public release artifacts, Chrome Web Store credentials, and updater-signature inputs.

Check posture

Main branch release automation remains healthy.
Recent release-extension-stage-controller runs succeeded on March 23, 2026 and March 24, 2026.
Local pnpm run perf:phase11:gate passed on March 24, 2026.
npm run release:promotion:readiness -- --version 0.1.0-beta.14 --channel staged_public_prerelease still reports status=blocked.

Blocking reality

• manual smoke marker still missing in docs/PHASE6_SMOKE_EVIDENCE.md
• internal-beta and chrome-store-public release manifests for 0.1.0-beta.14 are still missing
• Chrome Web Store credentials are still missing (CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN, CWS_EXTENSION_ID)
• updater signature input is still missing for the staged public prerelease flow

Done when

• The active Notion page and this governed issue describe the same slice.
• The current blockers are either resolved or replaced with fresher evidence-backed blockers.
• The next proof step for this project is captured through the governed GitHub lane.

[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.