Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-4046Done

motir.co serves /docs — the eight generated pages, the mechanism decided and recorded before they are written

Type: code · Executor: coding_agent · Repo: motir-marketing · ONE PR.

Render /docs on motir.co. The mechanism must be DECIDED and recorded BEFORE the pages are written — this is the card's first deliverable, not a detail.

The decision it owes first

The eight doc pages are GENERATED from motir-core's own registries — lib/apiDocs/reference reads the OpenAPI spec file, lib/apiDocs/mcp reads the tool catalogue. Rendering them here means consuming those registries across a repository boundary, which is the mirror-rot tests/navigation/proxy-matcher.test.ts exists to catch. Decide HOW and record it (an ADR in this repo, or the PR body) before writing the pages: a published artifact motir-core emits and this repo installs is the shape that does not rot; a copied spec with no guard is the shape that does.

Scope

  1. The eight pages (/docs, /docs/api, /docs/api/getting-started, /docs/api/stability, /docs/mcp, /docs/mcp/tools, /docs/cli, /docs/sandbox), matching what motir-core currently publishes.
  2. Whatever mechanism is chosen carries a guard that fails when this repo's copy drifts from motir-core's registries — a copied spec with no guard is not an acceptable outcome.
  3. Internalise the Docs nav item and footer link — DOCS in lib/destinations.ts becomes /docs (same-origin), matching MOTIR-3880's chrome.
  4. The crawl surface entries for these pages.

Boundary

  • It composes MOTIR-3880's chrome; redraws none of it.
  • It reads no database and adds no Prisma client / connection string (asserted).

Acceptance criteria

  • /docs renders on motir.co under one chrome, and its content matches what motir-core currently publishes.
  • The mechanism is decided and recorded before the pages are written, and carries a drift guard that fails when this repo's copy drifts from motir-core's registries.
  • DOCS in lib/destinations.ts is same-origin; tests/destinations.test.ts asserts it.
  • No database client / Prisma / connection string (asserted).
  • pnpm lint · format:check · typecheck · build · test pass; AA contrast holds in both themes.