fix(platform): reapply HIGH #6 + SA auth-gating + VULN-004 SHA enforcement after platform→workspace-server rename

[molecule-ai]

[backend-agent]

Summary

PR #954 (fix/launch-high6-cp-auth-token-boot) has been in CONFLICTING state since the platform/ → workspace-server/ rename (#479a027). This PR reapplies all five change sets from #954 to the correct new paths, resolving the conflict cleanly.

Changes ported from #954:

• GET /workspaces/:id auth-gating (SA security finding): Unauthenticated callers now receive only {id, name, agent_card:{name,description,version}}. Container URLs (agent_card.url, top-level url), current_task, active_tasks, and all topology fields are withheld. The endpoint returns 200 in both cases (not 401) so A2A peer discovery continues to work. Adds publicAgentCard() helper.

• HIGH Add admin endpoint to mint deterministic test tokens (follow-up to PR #5) #6 EC2 boot token race fix: provisionWorkspaceCP now issues the auth token BEFORE calling cpProv.Start() and injects it as MOLECULE_AUTH_TOKEN in the boot environment. Previously, issuing AFTER Start caused the EC2 instance's first /registry/register call to be treated as a re-registration (returning no token), leaving the agent stuck at provisioning forever with 401 heartbeats.

• Orphaned token revocation (security Q6): Both provisionWorkspaceOpts and provisionWorkspaceCP now use a startSucceeded defer pattern — if Start() fails, the freshly-issued token is revoked so it cannot be used by a never-launched workspace.

• Full SHA-only enforcement (VULN-004, issue security: plugin supply chain hardening — require pinned refs and SHA256 manifest integrity (SAFE-T1102) #768): github.go now rejects branch names and movable tags (in addition to empty refs). Only a full 40-character hex commit SHA passes. Uppercase SHAs are normalized to lowercase. SHA refs use the correct git init + git fetch + git checkout FETCH_HEAD protocol instead of git clone --branch (which doesn't accept commit SHAs).

• MOLECULE_AUTH_TOKEN bootstrap: workspace/platform_auth.py's get_token() reads the env var as a fallback after the .auth_token file, auto-persists it to disk (0600) on first use.

Test plan

• cd workspace-server && go test -race ./... — all packages
• Python: cd workspace && python -m pytest tests/test_platform_auth.py -v — MOLECULE_AUTH_TOKEN tests
• Verify CI passes on self-hosted macOS runner
• Confirm PR fix(platform): plugin supply-chain integrity + workspace endpoint auth + HIGH #6 boot token race #954 is closed/superseded

Related

• Supersedes/closes fix(platform): plugin supply-chain integrity + workspace endpoint auth + HIGH #6 boot token race #954 (CONFLICTING after platform→workspace-server rename)
• Fixes issue referenced in PR docs: staging environment design + Phase 36 + Tunnel migration plan #934, HIGH Add admin endpoint to mint deterministic test tokens (follow-up to PR #5) #6
• Part of supply-chain hardening VULN-004 (security: plugin supply chain hardening — require pinned refs and SHA256 manifest integrity (SAFE-T1102) #768)

🤖 Generated with Claude Code

[HongmingWang-Rabbit]

Closing — this PR duplicates and conflicts with the open-source cleanup work already merged:

• chore: open-source preparation — scrub secrets, add community files #940 (secrets scrub + community files)
• chore: final open-source cleanup — binary, stale paths, private refs #944 (binary removal + stale paths)
• chore: move internal docs to private repo #946 (internal docs moved to Molecule-AI/internal)
• chore: final cleanup — remove internal tooling, gitignore local config #947 (final cleanup)
• fix(plugins): wire VerifyManifestIntegrity into install pipeline #948 (VerifyManifestIntegrity wiring)
• fix(docs): update cd commands for workspace-server/ and workspace/ renames #950-953 (path fixes)

The changes in this PR (auth-gating, SHA enforcement, path renames) are either already on staging or need to be re-implemented on the current staging HEAD to avoid conflicts.