Epic: agents live outside the monorepo — enforce the platform-only boundary

[serge-ivo]

Principle

From docs/agent-platform-strategy.md:

The monorepo holds the platform only (runtime, tools, brain, marketplace, billing). Creator agents are either data or isolated code — never woven into the core. First-party runtime agents (Coder/apply) are the rare core-resident exception.

PAGS had drifted from this: 10 self-contained standalone-worker agents existed as duplicate inert copies under platform/agents/ (not pnpm workspace members, not typechecked, not deployed) and as their own ProAgentStore/<slug> repos (the real deploy unit, each with its own deploy.yml). Pure drift weight, untouched since the 2026-06 seed.

The correct model (three buckets)

Bucket	Agents	Home
Tier-0 — core-resident (platform imports/runs them)	coder (web UI imported by console), job-application-assistant (apply pipeline)	monorepo platform/agents/ (pnpm workspace members)
Tier-1 — config/data (D1/DO, no code)	repo-chat (seeded via migration 0032, runs in AgentDO)	monorepo (seed/migration) — data, not a worker
Standalone-worker (own CF Worker + deploy.yml)	site-monitor, lead-qualifier, content-pipeline, competitor-intel, support-escalator, data-analyst, meeting-notes, seo-auditor, invoice-parser, email-drafter, creator-os-agent, qa-automation, small-business-website-lead-finder	own ProAgentStore/<slug> repo, cloned locally to ~/dev/stores/pags/agents/<slug>/

Done (2026-08-01)

• Verified each of the 10 monorepo copies against its standalone repo (7 identical; invoice-parser/meeting-notes/seo-auditor had monorepo-only cosmetic biome/lint drift — pushed back to the standalone repos so those are canonical).
• Removed the 10 duplicate platform/agents/* dirs from the monorepo — commit f9980a8 on main.
• Kept coder, job-application-assistant, repo-chat.
• Updated docs/agent-platform-strategy.md (standalone agents live in own repos) and documented the local pags/agents/<slug>/ clone convention.

Remaining

• Verify each standalone-worker agent deploys from its own repo #48 — Verify each standalone-worker agent actually deploys from its own repo (the seed repos' deploy.yml has never run as the canonical path).
• CI guard: block new platform/agents/ folders outside the Tier-0 allowlist #49 — CI guard blocking new platform/agents/ folders outside the Tier-0 allowlist (drift prevention).
• Decide repo-chat's canonical form: the strategy doc says Tier-1 config/data agents are "no code, no commit" — does it still warrant a platform/agents/repo-chat/ folder, or should it be migration/seed-only?
• (Phase 3, later) Converge Tier-0 agents onto the shared multi-tenant runtime so "first-party" stops meaning "special-cased in the monorepo" — see strategy doc build-order Issues → Kanban: a provider-agnostic task board with GitHub-issue import #4.

[serge-ivo]

Closing the platform-only boundary epic as implemented. The monorepo now keeps only Tier-0 first-party agent sources in agents/, the allowlist guard landed in #49, and README documents that other catalog agents live outside this repo. Standalone deploy verification remains tracked separately by #48.

[serge-ivo]

Implementation links: no associated PR was found; this landed direct on main across f9980a8 and fe7cdf5. Remaining standalone deploy verification stays in #48.