test(e2e): template-asset delivery gate — fresh seo-agent must boot WITH skills (RFC #2843) #2971
Reference in New Issue
Block a user
Delete Branch "feat/template-delivery-e2e-gate"
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?
RFC #2843 regression gate — fresh seo-agent must boot WITH its skills
Nothing in CI provisions a fresh agent end-to-end and inspects the delivered
/configs. That blind spot is exactly why the 2026-06-15 incident family shipped green:agent-skills/— #32 (the seo-all skill pack, the whole point of the agent, is missing)I confirmed #3 empirically: a fresh
seo-agentprovisioned on the current image getsconfig.yaml(8429 B real) +prompts/seo-agent.md+ model, but/configs/agent-skills/is empty.What this adds
tests/e2e/test_template_delivery_e2e.sh— provisions a throwaway tenant + a freshseo-agenttemplate workspace, then asserts delivery, one assertion per incident:onlineGET /model== declared modelconfig.yamldelivered + real (>1 KiB, not the 218 B stub)prompts/deliveredagent-skills/seo-all/SKILL.mddeliveredTeardown trap deletes the org even on failure. Mirrors the auth/provision/teardown shape of
test_staging_concierge_e2e.sh.Staged rollout (intentional — do not flip to required yet)
continue-on-error), path-filtered to delivery code. It will report RED while #2955 and #32 are open — that's the point: it proves the gate correctly detects the bug.continue-on-errorand add to branch-protectionrequired_status_checks→ merge-blocking.🤖 Generated with Claude Code