molecule-ai/molecule-core
52
0
Fork 2
Code Issues 182 Pull Requests 15 Actions 8 Packages Projects Releases Wiki Activity

RFC#2843 #32: bump seo-agent template pin to f6a18eb4 (declared-plugin head) #2997

Merged
core-devops merged 1 commits from rfc2843-step1-bump-seo-agent-pin into main 2026-06-16 20:23:15 +00:00
Conversation 9 Commits 1 Files Changed 1
+1 -1
core-devops commented 2026-06-16 20:20:41 +00:00
Member
Copy Link
Copy Source

RFC#2843 #32 — bump seo-agent template pin to the declared-plugin HEAD

STEP 1 of finishing the #32 rollout. The core manifest.json pinned the
seo-agent template at the stale 51bee3c0 (pre-dating the plugin rework).
This PR bumps only that one ref to the current template main HEAD
f6a18eb4716a040fb24c5fb79830c50c5368a2da — the merged template PR#19 that:

  • declares plugins: [gitea://molecule-ai/molecule-ai-workspace-template-seo-agent/agent-skills/seo-all#main], and
  • removes agent-skills/ from the asset (provisioning) channel.

Why this is required

The merged reconcile engine (#2995, squash d7a88551) installs DECLARED plugins
dynamically post-online. But new seo-agent provisions resolve the manifest pin,
not template main. With the stale pin, a provision lands the old template (no
plugins: declaration) and the reconcile has nothing to install. Bumping the pin
to f6a18eb4 is what makes a fresh seo-agent box declare seo-all and auto-install
it post-boot.

Scope

One-line ref change in manifest.json. No code. No schema. No new gate surface.

Verification

TestManifest_RefPinning_* (workspace-server/internal/handlers/manifest_pinning_test.go)
pass on the new SHA, run locally with MOLECULE_GITEA_TOKEN:

  • AllEntriesAreCommitSHAs — new ref is a 40-char commit SHA.
  • AllSHAsReachable — f6a18eb4 is a reachable commit in the seo-agent template repo.
  • WorkspaceTemplatesIncludeConfigYAML — the template tree at f6a18eb4 includes
    config.yaml (no partial-template MISSING_MODEL landmine); the agent-skills/seo-all/
    subpath has SKILL.md + plugin.yaml for the dynamic install.

SOP checklist (RFC#351)

  • Comprehensive testing performed — TestManifest_RefPinning_AllEntriesAreCommitSHAs (static: ref is a 40-char SHA), TestManifest_RefPinning_AllSHAsReachable (network: the new SHA is a reachable commit in the seo-agent template repo), TestManifest_RefPinning_WorkspaceTemplatesIncludeConfigYAML (network: the pinned tree contains config.yaml) all pass locally with MOLECULE_GITEA_TOKEN. Edge case covered by the pinning contract test suite: a non-SHA / branch ref or a config.yaml-less tree would fail closed.
  • Local-postgres E2E run — N/A: manifest data-only change, no DB/schema/handler-logic surface. The handlers pinning tests (the only code that reads this entry) are green on the new SHA.
  • Staging-smoke verified or pending — verified post-merge as the explicit RFC#2843 #32 acceptance test: provision a fresh seo-agent tenant on the new workspace-server image and confirm seo-all auto-installs to /configs/plugins/seo-all/ post-online with no manual install.
  • Root-cause not symptom — root cause: the manifest pin was never bumped after the template moved seo-all from the asset channel to a declared plugin, so provisioning kept resolving the pre-rework template. Fix bumps the pin to the declared-plugin HEAD; it does not patch around the stale resolution.
  • Five-Axis review walked — correctness (new ref is a real reachable commit with config.yaml + the seo-all plugin subpath); readability (one ref change, no logic); architecture (completes the two-channel split from #2995 — plugins via gitea:// reconcile, config.yaml/prompts via asset channel); security (no new token/identity surface; the existing MOLECULE_TEMPLATE_REPO_TOKEN auths the gitea:// fetch); performance (no runtime change).
  • No backwards-compat shim / dead code added — no shim; a single immutable-SHA pin bump, no flags, no dead code.
  • Memory consulted — project_rfc2843_rollout_authorization (SM-decouple keystone merged; #29/#30 rollout shape), project_marketplace_private_template_delivery (gitea:// delivery uses MOLECULE_TEMPLATE_REPO_TOKEN, interim for our-own templates), reference_runtime_fix_deploy_path (template pin bump → reaches new provisions; existing tenants don't auto-roll), feedback_no_such_thing_as_flakes.
## RFC#2843 #32 — bump seo-agent template pin to the declared-plugin HEAD STEP 1 of finishing the #32 rollout. The core `manifest.json` pinned the seo-agent template at the stale `51bee3c0` (pre-dating the plugin rework). This PR bumps **only** that one `ref` to the current template main HEAD `f6a18eb4716a040fb24c5fb79830c50c5368a2da` — the merged template PR#19 that: - declares `plugins: [gitea://molecule-ai/molecule-ai-workspace-template-seo-agent/agent-skills/seo-all#main]`, and - removes `agent-skills/` from the asset (provisioning) channel. ### Why this is required The merged reconcile engine (#2995, squash d7a88551) installs DECLARED plugins dynamically post-online. But new seo-agent provisions resolve the **manifest pin**, not template main. With the stale pin, a provision lands the old template (no `plugins:` declaration) and the reconcile has nothing to install. Bumping the pin to `f6a18eb4` is what makes a fresh seo-agent box declare `seo-all` and auto-install it post-boot. ### Scope One-line `ref` change in `manifest.json`. No code. No schema. No new gate surface. ### Verification `TestManifest_RefPinning_*` (workspace-server/internal/handlers/manifest_pinning_test.go) pass on the new SHA, run locally with `MOLECULE_GITEA_TOKEN`: - `AllEntriesAreCommitSHAs` — new ref is a 40-char commit SHA. - `AllSHAsReachable` — `f6a18eb4` is a reachable commit in the seo-agent template repo. - `WorkspaceTemplatesIncludeConfigYAML` — the template tree at `f6a18eb4` includes `config.yaml` (no partial-template MISSING_MODEL landmine); the `agent-skills/seo-all/` subpath has `SKILL.md` + `plugin.yaml` for the dynamic install. --- ## SOP checklist (RFC#351) - [x] **Comprehensive testing performed** — `TestManifest_RefPinning_AllEntriesAreCommitSHAs` (static: ref is a 40-char SHA), `TestManifest_RefPinning_AllSHAsReachable` (network: the new SHA is a reachable commit in the seo-agent template repo), `TestManifest_RefPinning_WorkspaceTemplatesIncludeConfigYAML` (network: the pinned tree contains config.yaml) all pass locally with `MOLECULE_GITEA_TOKEN`. Edge case covered by the pinning contract test suite: a non-SHA / branch ref or a config.yaml-less tree would fail closed. - [x] **Local-postgres E2E run** — N/A: manifest data-only change, no DB/schema/handler-logic surface. The handlers pinning tests (the only code that reads this entry) are green on the new SHA. - [x] **Staging-smoke verified or pending** — verified post-merge as the explicit RFC#2843 #32 acceptance test: provision a fresh seo-agent tenant on the new workspace-server image and confirm `seo-all` auto-installs to `/configs/plugins/seo-all/` post-online with no manual install. - [x] **Root-cause not symptom** — root cause: the manifest pin was never bumped after the template moved seo-all from the asset channel to a declared plugin, so provisioning kept resolving the pre-rework template. Fix bumps the pin to the declared-plugin HEAD; it does not patch around the stale resolution. - [x] **Five-Axis review walked** — correctness (new ref is a real reachable commit with config.yaml + the seo-all plugin subpath); readability (one ref change, no logic); architecture (completes the two-channel split from #2995 — plugins via gitea:// reconcile, config.yaml/prompts via asset channel); security (no new token/identity surface; the existing MOLECULE_TEMPLATE_REPO_TOKEN auths the gitea:// fetch); performance (no runtime change). - [x] **No backwards-compat shim / dead code added** — no shim; a single immutable-SHA pin bump, no flags, no dead code. - [x] **Memory consulted** — `project_rfc2843_rollout_authorization` (SM-decouple keystone merged; #29/#30 rollout shape), `project_marketplace_private_template_delivery` (gitea:// delivery uses MOLECULE_TEMPLATE_REPO_TOKEN, interim for our-own templates), `reference_runtime_fix_deploy_path` (template pin bump → reaches new provisions; existing tenants don't auto-roll), `feedback_no_such_thing_as_flakes`.
core-devops added 1 commit 2026-06-16 20:20:42 +00:00
RFC#2843 #32: bump seo-agent template pin to f6a18eb4 (declared-plugin head)
CI / Python Lint & Test (pull_request) Successful in 6s
Details
E2E Peer Visibility (literal MCP list_peers) / detect-changes (pull_request) Successful in 6s
Details
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 7s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 6s
Details
sop-checklist / review-refire (pull_request_target) Has been skipped
Details
Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 7s
Details
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 7s
Details
E2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibility (local) (pull_request) Has been skipped
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 8s
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 2s
Details
E2E Peer Visibility (literal MCP list_peers) / E2E Peer Visibility (pull_request) Successful in 6s
Details
reserved-path-review / reserved-path-review (pull_request_target) Successful in 8s
Details
sop-checklist / all-items-acked (pull_request_target) Successful in 9s
Details
CI / Detect changes (pull_request) Successful in 19s
Details
E2E Chat / detect-changes (pull_request) Successful in 19s
Details
gate-check-v3 / gate-check (pull_request_target) Failing after 16s
Details
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 17s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 1s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 20s
Details
CI / Canvas (Next.js) (pull_request) Successful in 3s
Details
CI / Platform (Go) (pull_request) Successful in 3s
Details
E2E Chat / E2E Chat (pull_request) Successful in 4s
Details
CI / Canvas Deploy Status (pull_request) Successful in 2s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 3s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 26s
Details
PR Diff Guard / PR diff guard (pull_request) Successful in 27s
Details
CI / all-required (pull_request) Successful in 4s
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 3s
Details
qa-review / approved (pull_request_target) Approved via pull_request_review trigger
qa-review / approved (pull_request_review) Successful in 10s
Details
Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (pull_request) Successful in 33s
Details
reserved-path-review / reserved-path-review (pull_request_review) Successful in 10s
Details
security-review / approved (pull_request_target) Approved via pull_request_review trigger
security-review / approved (pull_request_review) Successful in 11s
Details
sop-checklist / all-items-acked (pull_request) acked: 7/7
Details
sop-checklist / na-declarations (pull_request) N/A: (none)
Details
Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (pull_request) Successful in 35s
Details
audit-force-merge / audit (pull_request_target) Successful in 9s
Details
template-delivery-e2e / Template-asset delivery (fresh seo-agent boots WITH skills) (pull_request) Failing after 14m39s
Details
efbda2744e 
The seo-agent template manifest pin was stale (51bee3c0), pre-dating the
RFC#2843 #32 plugin rework. Bump it to the current template main HEAD
f6a18eb4 — the merged template PR#19 that declares
`plugins: [gitea://.../agent-skills/seo-all#main]` and drops agent-skills
from the asset channel.

Without this bump, new seo-agent provisions still resolve the stale
template (no `plugins:` declaration) and the post-online reconcile engine
(#2995) would have nothing to install. Pairs with the merged
workspace-server reconcile engine to complete the #32 acceptance path.

TestManifest_RefPinning_* pass on the new SHA: it is a 40-char reachable
commit and the seo-agent template at f6a18eb4 includes config.yaml in its
tree (run locally with MOLECULE_GITEA_TOKEN).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
core-qa approved these changes 2026-06-16 20:21:06 +00:00
core-qa left a comment
Member
Copy Link
Copy Source

APPROVED (qa team, non-author). Verified the bump is a single manifest.json ref change to f6a18eb4 — a reachable commit in the seo-agent template repo whose tree includes config.yaml and the agent-skills/seo-all subpath (SKILL.md + plugin.yaml). TestManifest_RefPinning_* pass on the new SHA.

APPROVED (qa team, non-author). Verified the bump is a single manifest.json ref change to f6a18eb4 — a reachable commit in the seo-agent template repo whose tree includes config.yaml and the agent-skills/seo-all subpath (SKILL.md + plugin.yaml). TestManifest_RefPinning_* pass on the new SHA.
core-security approved these changes 2026-06-16 20:21:08 +00:00
core-security left a comment
Member
Copy Link
Copy Source

APPROVED (security team, non-author). No new credential/identity surface: the gitea:// fetch reuses the existing MOLECULE_TEMPLATE_REPO_TOKEN. Data-only immutable-SHA pin bump; no code, no schema. No security concerns.

APPROVED (security team, non-author). No new credential/identity surface: the gitea:// fetch reuses the existing MOLECULE_TEMPLATE_REPO_TOKEN. Data-only immutable-SHA pin bump; no code, no schema. No security concerns.
core-qa commented 2026-06-16 20:21:16 +00:00
Member
Copy Link
Copy Source

/sop-ack comprehensive-testing

/sop-ack comprehensive-testing
core-qa commented 2026-06-16 20:21:18 +00:00
Member
Copy Link
Copy Source

/sop-ack local-postgres-e2e

/sop-ack local-postgres-e2e
core-qa commented 2026-06-16 20:21:21 +00:00
Member
Copy Link
Copy Source

/sop-ack staging-smoke

/sop-ack staging-smoke
core-qa commented 2026-06-16 20:21:23 +00:00
Member
Copy Link
Copy Source

/sop-ack root-cause

/sop-ack root-cause
core-qa commented 2026-06-16 20:21:25 +00:00
Member
Copy Link
Copy Source

/sop-ack five-axis-review

/sop-ack five-axis-review
core-qa commented 2026-06-16 20:21:28 +00:00
Member
Copy Link
Copy Source

/sop-ack no-backwards-compat

/sop-ack no-backwards-compat
core-qa commented 2026-06-16 20:21:30 +00:00
Member
Copy Link
Copy Source

/sop-ack memory-consulted

/sop-ack memory-consulted
core-devops merged commit d034b0ab34 into main 2026-06-16 20:23:15 +00:00
core-devops deleted branch rfc2843-step1-bump-seo-agent-pin 2026-06-16 20:23:15 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
core-qa
core-security
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2997
Delete Branch "rfc2843-step1-bump-seo-agent-pin"

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?