Repository navigation
Error Codes manifest
github-actions[bot] edited this page Nov 16, 2026
·
2 revisions
Part of Error codes: every code @ultimat3/manifest registers. x errors explain <CODE> --json prints the same row.
| Code | Means | Typical cause | Fix |
|---|---|---|---|
X_AGENTS_MD_MISSING |
no AGENTS.md
|
the human-authored file was deleted | write it by hand — short: stack, commands, conventions |
X_AGENTS_MD_TOO_LARGE |
AGENTS.md grew past its cap |
generated facts pasted into it | move facts into x.manifest.json; keep conventions only |
X_MANIFEST_BREAKING |
a published contract was removed or narrowed | a breaking change with no version bump |
bun pm pkg set version=2.0.0 — the committed major plus one, in package.json (a 0.x app: 1.0.0, or re-commit the baseline with x manifest) — or restore the contract |
X_MANIFEST_DRIFT |
a committed manifest differs from the code | a primitive changed without regenerating, or the file was hand-edited so its buildId no longer hashes its own contents |
x manifest — bun run manifest for this repo's own framework.manifest.json
|
X_MANIFEST_FACT_INVALID |
a manifest fact is a number JSON cannot write back | a declaration handed the manifest NaN, Infinity or -0 (a route budget, a rate limit, a retry count); JSON writes it as null or 0, so the committed file could never match its own buildId and every build read as drift | set the declaration behind meta.path to 0 when meta.value is -0, otherwise to a finite number, then run x manifest |
Ultimate — v31.43.0 As of 2026-10. The full-stack framework where the primary developer is an AI agent: bunx create-ultimate myapp → Getting started · live demo. MIT licensed. What npm serves is npm view @ultimat3/core version, never this line, and this footer is the only page that stamps a version.
Repository · Issues · Changelog · llms.txt
Edits to these pages are synced from wiki/ in the repository — change the file there, not the wiki, or the next sync overwrites it.
Start
- Getting started
- Installation
- Shapes
- Bare VM
- Project layout
- Migrating an existing app
- Compared to other stacks
Tutorials
- 1 · First app
- 2 · First feature
- 3 · Auth and admin
- 4 · Jobs and realtime
- 5 · Deploy free
- 6 · Growing up
Primitives
- The eight primitives
- Building your own base
- Actions
- Entities and migrations
- Policies and authz
- Queries and live queries
- Client data
- Jobs and workflows
- Scheduled tasks
- Routes and render modes
Capabilities
- Realtime
- Caching and invalidation
- Batching and preloading
- N+1 detection
- PWA and offline
- Client navigation
- MCP and AI
- Agents
- Admin dashboard
- Scraping
- Auth
- Notify
- Storage and uploads
- Feature flags
- SEO
- Static assets
Cross-cutting
- I18n
- Theming
- UI components
- Interface rules
- Timezones and dates
- Money
- Outbound HTTP
- Resource management
- Migrations and backfills
- Testing
- CI: the gate across parallel jobs
Reference