chore: sync FPF spec from ailev/FPF (2026-05-20)#136
chore: sync FPF spec from ailev/FPF (2026-05-20)#136github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
chore/sync-fpf-eb283209
branch
from
27361d6 to
aba4d49
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aba4d49dee
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "slug": "boundary-unpacking-and-claim-decomposition", | ||
| "title": "Boundary unpacking and claim decomposition", | ||
| "staticPath": "/generated/routes/route_boundary-unpacking-and-claim-decomposition" |
There was a problem hiding this comment.
This sync replaces route:boundary-unpacking-claim-routing with route:boundary-unpacking-and-claim-decomposition, but the runtime still hard-codes the old ID for intent scoring and tailored guidance (src/runtime/query-helpers.ts and src/runtime/answer-projector.ts), and onboarding docs still tell users to select the old ID (docs/start-here.md, docs/work-packets.md, docs/mcp-recipes.md). After this change, those selectors no longer resolve to an existing route in the published snapshot, so boundary-unpacking queries lose deterministic routing and route-specific output quality.
Useful? React with 👍 / 👎.
Auto-detected new commit on
ailev/FPFmain.eb2832093c1e482d5fdd4985c3d2011ab240b429CI gates this merge: lint, type, tests, hosted MCP build, Vercel preview deploy, and Playwright E2E. After a two-hour review window, the sync workflow will merge this PR automatically if every reported check/status is passing.