Reconcile resident content pipeline and Factory onboarding

CLAUDE.md

@@ -0,0 +1,20 @@
+## Resident lead
+
+The resident `agentrelay-com` agent owns this repo — the front door
+(marketing site, docs, router) — and the **content pipeline**. Reports to
+**cmo** (Will → chief → cmo → agentrelay-com); chief for escalations.
+
+**Content pipeline:** `content/pipeline.md` is the running list of blog
+posts — one entry per idea, statuses `idea → notes → ready-for-will →
+drafting → published`. Ideas arrive by DM from Will, chief, or cmo; every
+idea gets an entry the moment it arrives. Developing an idea means
+research-backed notes a human can write from: the argument, the beats,
+evidence/links, suggested title options — never a finished post; Will
+writes the human form. Flag entries `ready-for-will` and DM cmo when they
+are.
+
+One writer while resident; delegates in worktrees off origin/main.
+Session start: this file, content/pipeline.md, `git status`,
+`git log --oneline -15`, relay inbox. ACK / progress / DONE with
+evidence. **Anything going live — deploys, publishing posts, DNS —
+is gated on cmo.**

README.md

@@ -16,7 +16,7 @@ web/      Next.js marketing + docs site (OpenNext → Cloudflare Workers)
 
 ```bash
 npm install         # workspace root
-npm run dev         # next dev
+npm run dev         # next dev on http://localhost:24368
 npm run build       # next build
 npm test            # vitest
 npm run preview     # build + run the OpenNext worker locally (wrangler dev)

content/pipeline.md

@@ -0,0 +1,73 @@
+# Content pipeline — running list
+
+Statuses: idea → notes → ready-for-will → drafting → published. Newest
+first. One `##` entry per post; body holds the notes.
+
+*(entries begin below)*
+
+## Just in time Graphs
+
+- Status: idea
+- Source: untracked local
+  `web/content/blog/build-your-first-agent-team.mdx`
+- State: only the title is unique. The description is empty and the body
+  is a duplicate of “Build Your First Team of AI Agents,” so there is no
+  usable draft or argument to preserve yet.
+- Reconciliation: retain this as a pipeline idea, but do not publish or
+  treat the duplicated body as notes. Ask Will what “just in time
+  graphs” means before developing it.
+
+## Hosted onboarding skill: node CLI group
+
+- Status: published
+- Source: clean `skill-page-v11-cli` worktree
+- Artifact: `web/content/agent-relay/SKILL.md`
+- Evidence: PR
+  [#34](https://github.com/AgentWorkforce/agentrelay.com/pull/34) merged
+  2026-07-30 as commit `470adf1`.
+- Reconciliation: worktree commit `8054dc3` is the content that shipped.
+  Its unmerged follow-up `d563bfb` says MCP callers must explicitly
+  register; that now contradicts broker auto-registration and should not
+  be carried forward.
+
+## Build Your First Team of AI Agents
+
+- Status: drafting
+- Source: Will's clean `blog/first-agent-team` worktree and open PR
+  [#28](https://github.com/AgentWorkforce/agentrelay.com/pull/28)
+- Artifact: `web/content/blog/build-your-first-agent-team.mdx`
+- State: a complete 347-line playbook draft exists, covering the
+  five-role team, harness routing, named-agent anatomy, Relay setup,
+  adversarial review loop, and first-week staffing order.
+- Reconciliation: the untracked `copy.mdx` carries this title but
+  duplicates the same body; the committed worktree/PR is canonical, so
+  delete the local copy rather than creating another post.
+
+## You're not behind: how I got out of the agent-factory overwhelm
+
+- Status: idea
+- Source: Will, relayed verbatim by chief on 2026-07-29
+- Form: undecided — essay or Twitter/X thread; notes should develop both
+  cuts and recommend one
+- Voice seeds: Most people on Twitter purport to have huge agent
+  factories — “their most efficient agent workflows, everybody else is
+  doing it wrong, the way they do it is right, you're falling behind.”
+  Counter-position: “that's not actually me.” If you're like Will:
+  overwhelmed, producing all this extra agent code, feeling you need to
+  stay on top of it, feeling you can't, “slow letting go.”
+- Core promise: give people hope. They are not behind; they can handle
+  it, and there are tools. Keep it explicitly testimonial and
+  anti-prescriptive: “here's how I got out of that, here's how I DID it
+  — not here's how you SHOULD do it.”
+- Notes to develop:
+  - Subvert the confident factory-flex genre with a couple of anonymized
+    archetypes; do not name or dunk on individuals.
+  - Build the emotional arc from overwhelm, to permission not to stay on
+    top of everything, to letting go through structure.
+  - Ground “how I did it” in Will's real machinery: a chief-of-staff
+    agent, departments with owners, one-writer file discipline,
+    dispatch-only work, briefs with ACK/DONE, and a markdown brain in
+    git. Ask chief for journal/workstream specifics rather than
+    inventing them.
+  - Offer anti-guru title options.
+  - Develop both the thread cut and essay cut, then recommend.

teams.json

@@ -0,0 +1 @@
+{"team":"agentrelay-com","autoSpawn":true,"agents":[{"name":"agentrelay-com","cli":"codex","role":"resident lead — agentrelay.com front door + content pipeline","task":"Read the agent guide fully (including the Resident lead section) and follow the session-start ritual (guide, content/pipeline.md, git status, recent git log, relay inbox). You are the resident agentrelay.com lead: stay online, answer DMs from cmo, chief, and Will, log every blog idea that arrives into content/pipeline.md immediately, and never self-remove. Assignments arrive from cmo (chief for bootstrap). ACK on start, DONE with evidence. Deploys/publishing gated on cmo."}]}

web/package.json

@@ -7,10 +7,10 @@
     "node": ">=20.9.0"
   },
   "scripts": {
-    "dev": "next dev --webpack",
+"dev": "next dev --webpack --port 24368",
     "prebuild": "node scripts/generate-setup-skills.mjs",
     "build": "next build --webpack",
-    "start": "next start",
+    "start": "next start --port 24368",
     "test": "vitest run",
     "test:e2e": "playwright test",
     "precf:build": "node scripts/generate-setup-skills.mjs",