Commit graph

6 commits

Author SHA1 Message Date
Bryan Helmkamp
6836aebc0c
docs(changelog): refresh recent product changes 2026-05-06 07:39:09 -04:00
Bryan Helmkamp
bd82366e6b
fix(docs): point docs.json to renamed stage events endpoint (#217)
## Summary
- `docs.json` referenced `GET /api/v1/runs/{id}/stages/{stageId}/turns`,
but that operation was renamed to `/events` in `fabro-api.yaml` between
the last passing and first failing Mintlify deploy.
- Mintlify could not resolve the operation under the API Reference tab
and reported `Failed to fetch OpenAPI file for anchor or tab`, failing
every docs deploy on `main` since commit `e40dc7d9a`.

## Verification
- Cross-checked every operation page reference in
`docs/public/docs.json` against operations defined in
`docs/public/api-reference/fabro-api.yaml`; all references now resolve.

## Test plan
- [ ] Mintlify Deployment check turns green on this PR
- [ ] After merge, https://docs.fabro.sh updates and the API Reference >
Run Internals group shows the renamed `List Stage Events` endpoint

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-05 16:10:25 -04:00
Bryan Helmkamp
31cbdb5c31
docs(changelog): refresh recent product changes 2026-05-04 11:38:55 -04:00
Bryan Helmkamp
b96647314c
docs(deployment): split into local vs self-hosted, drop Render/Fly/DO
Reframe the deployment docs around the actual product story: Fabro
runs as a server, and the only deployment question is where that
server runs (laptop vs self-hosted Docker). Drop the Render, Fly.io,
and DigitalOcean guides and their config files; keep Railway as the
managed shortcut.

- New: administration/deployment.mdx (overview, two-mode framing)
- New: administration/self-host-docker.mdx (compose-first how-to)
- Move: administration/deploy-server.mdx -> reference/server-operations.mdx
  (it was operational reference, not deploy guidance)
- Delete: deploy-render.mdx, deploy-fly-io.mdx, deploy-digital-ocean.mdx
- Delete: render.yaml, fly.toml, railway.toml, Dockerfile.deploy
- docker-compose.yaml: load .env if present so users can drive the
  stack from a single env file end-to-end
- Update internal links and the docs-test that pinned the old path
2026-05-01 09:26:35 -04:00
Bryan Helmkamp
c8185eaee6
docs(changelog): refresh recent product changes 2026-04-30 08:11:08 -04:00
Bryan Helmkamp
283eab181f
refactor(docs): split docs/ into public/ and internal/
Invert the docs convention so the Mintlify-published site lives under
docs/public/ and internal artifacts (strategy docs, brainstorms, plans,
etc.) sit at docs/ root or docs/internal/. Tools that default to writing
into docs/ now land in the catch-all instead of leaking into the
published tree.

- Move Mintlify content (administration/, agents/, api-reference/,
  changelog/, core-concepts/, examples/, execution/, getting-started/,
  human-tools/, integrations/, languages/, reference/, tutorials/,
  workflows/, images/, logo/, docs.json, favicon.svg, dot-highlight.js)
  into docs/public/.
- Collapse docs-internal/ into docs/internal/.
- Update Rust path references (fabro-api/build.rs, fabro-server,
  fabro-dev), TypeScript generator arg, CI path filters, clippy.toml
  reasons, AGENTS.md/CLAUDE.md, and README.md image refs.

Mintlify dashboard project root must be updated to docs/public/ in a
follow-up. .mintignore move/trim and .claude/skills/ updates land in a
separate commit.
2026-04-27 07:21:13 -07:00
Renamed from docs/docs.json (Browse further)