molecule-ai/molecule-core
52
0
Fork 2
Code Issues 185 Pull Requests 14 Actions Packages Projects Releases Wiki Activity

[main-red] E2E Peer Visibility parent workspace create omits required model #2212

New Issue
Closed
opened 2026-06-04 05:40:12 +00:00 by molecule-code-reviewer · 0 comments
molecule-code-reviewer commented 2026-06-04 05:40:12 +00:00
Member
Copy Link
Copy Source

MECHANISM: molecule-core main 7f25373309ec fails in E2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibility (push) before the actual peer-visibility assertion runs. .gitea/workflows/e2e-peer-visibility.yml:167-168 invokes tests/e2e/test_peer_visibility_mcp_staging.sh; the script creates the parent workspace at tests/e2e/test_peer_visibility_mcp_staging.sh:200-202 with runtime":"claude-code" and secrets, but no model or template. Staging now enforces the workspace-create contract: no platform-side default model for this runtime.

EVIDENCE: run 206728, job 275414, head 7f25373309ec. Log excerpt: MODEL_REQUIRED ... model is required and has no platform-side default. The tenant provision and health preflight succeeded first: org 627ca84d-4094-4e5e-9cee-ff3fbd3bbda7, tenant buildinfo 793d376a1a30..., then parent create failed. Combined status on head is failure; controlplane main 96f03878a95d is green in the same scan.

RECOMMENDED FIX SHAPE: update molecule-core tests/e2e/test_peer_visibility_mcp_staging.sh parent/sibling workspace create payloads, or the associated runtime template contract, so every workspace create in this E2E passes an explicit registered model/template compatible with staging. Keep the literal MCP list_peers assertion unchanged; this is a setup-contract failure, not a peer-visibility verdict.

MECHANISM: molecule-core main `7f25373309ec` fails in `E2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibility (push)` before the actual peer-visibility assertion runs. `.gitea/workflows/e2e-peer-visibility.yml:167-168` invokes `tests/e2e/test_peer_visibility_mcp_staging.sh`; the script creates the parent workspace at `tests/e2e/test_peer_visibility_mcp_staging.sh:200-202` with `runtime":"claude-code"` and `secrets`, but no `model` or template. Staging now enforces the workspace-create contract: no platform-side default model for this runtime. EVIDENCE: run `206728`, job `275414`, head `7f25373309ec`. Log excerpt: `MODEL_REQUIRED ... model is required and has no platform-side default`. The tenant provision and health preflight succeeded first: org `627ca84d-4094-4e5e-9cee-ff3fbd3bbda7`, tenant buildinfo `793d376a1a30...`, then parent create failed. Combined status on head is `failure`; controlplane main `96f03878a95d` is green in the same scan. RECOMMENDED FIX SHAPE: update molecule-core `tests/e2e/test_peer_visibility_mcp_staging.sh` parent/sibling workspace create payloads, or the associated runtime template contract, so every workspace create in this E2E passes an explicit registered model/template compatible with staging. Keep the literal MCP `list_peers` assertion unchanged; this is a setup-contract failure, not a peer-visibility verdict.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2212
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?