docs(agents): correct the documented docs dev-server port to 3000

[os-elon]

Fixes#97

AGENTS.md § Commands documented the docs dev server on http://localhost:3001. It binds 3000. Exactly one of the two had to change; this PR changes the doc, and the evidence for that direction is below.

Which side is wrong

The doc — not a close call once the repository's own port map is in view.

1. .claude/launch.json already assigns these ports, and it gives 3001 to something else. It was added in the initial commit 32894a5, the same commit that wrote the AGENTS.md line:

configuration	port
Docs site (@objectos/docs)	3000 (autoPort: true)
ObjectStack server (@objectos/server)	3001

So 3001 is the server's number in this repo, not a deliberate "keep the docs site off the platform's port" choice made for the docs site. @objectos/server was removed when the repository was repositioned as the docs front door (PR #38), which is why nothing answers on 3001 today.

2. The script has never bound 3001.apps/docs/package.json has carried bare "dev": "next dev" in every commit of this repository's history — git show 32894a5:apps/docs/package.json is already bare, and only two commits have ever touched that file, neither adding -p. The documented port was never true of any commit. This is not drift away from a setup that once worked.

3. Two READMEs already say 3000.README.md (pnpm docs:dev # Fumadocs site at http://localhost:3000) and apps/docs/README.md (pnpm --filter @objectos/docs dev # localhost:3000). AGENTS.md was the lone outlier: one statement against three.

4. The alternative spreads the inconsistency instead of closing it. Pinning next dev -p 3001 would make the AGENTS.md line true, but in the same stroke move the docs server onto the port launch.json reserves for @objectos/server and make both READMEs false. The one-word doc change makes all four statements agree.

The case for 3001, and why it does not survive

The published corpus does consistently put the platform on localhost:3000 — index.mdx, quickstart.mdx, build/marketplace.mdx, configure/mcp.mdx, configure/storage.mdx, resources/faq.mdx — which makes 3001 look like deliberate collision-avoidance. But the platform on 3000 there is the reader's own ObjectOS runtime, started from their own project (.env.example: OBJECTOS_PORT=3000, the host port published by docker-compose). It is not a process that runs in this repository. The process that did run here was @objectos/server, and launch.json pinned it to 3001, never 3000. There is no in-repo process for the docs dev server to collide with, and 3001 is the one number already spoken for.

Measured

The dev server was started unmodified in this branch's worktree and allowed to report its own port:

> @objectos/docs@0.0.0 dev /home/user/objectos-issue-97/apps/docs
> next dev
▲ Next.js 16.2.6 (Turbopack)
- Local: http://localhost:3000
✓ Ready in 424ms

While it was up: curl http://localhost:3000/ returned 307 with location: /docs; curl http://localhost:3001/ returned 000 (connection refused). After a clean stop, 3000 also returned 000. This reproduces the measurement in the issue on a second machine and a later base commit.

Verification

Run at 0846b45, the commit this PR proposes. Every turbo task forced (--force) and its log paths confirmed to be this worktree, so nothing here is a replayed cache entry from a sibling checkout. Local Node is v22.22.2, matching the Node 22 that CI adopted in #118.

gate	result
pnpm install --frozen-lockfile	pass
pnpm turbo run type-check --continue --force	pass, 1 task
pnpm turbo run build --force	pass, 1 task
pnpm turbo run test --force	pass, 1 task
node .github/scripts/check-translations.mjs	pass
node .github/scripts/check-translation-ownership.mjs	pass, 0 translation artifacts touched
node .github/scripts/check-translation-output.mjs --files	pass, 133 findings all pre-existing and unscoped to this diff
node .github/scripts/check-translation-output.mjs --self-test	pass, 20 cases

The Translations workflow will not actually run on this PR: its paths filter is content/docs/**, apps/docs/lib/i18n.ts, .github/scripts/check-translation*.mjs and its own file, none of which this diff touches. It was run locally anyway. deploy-docs.yml is push-to-main and its paths do not include AGENTS.md, so it stays idle on merge too.

Scope

One line in one file. No script reordering, no other AGENTS.md edits, no content changes.

AGENTS.md is governed surface, so this stays in draft for the maintainer to merge. That cost was known before the direction was chosen and did not influence it — the cheaper route was the one available by editing apps/docs/package.json, and the evidence pointed the other way.

---

Generated by Claude Code