chore: sync FPF spec from ailev/FPF (2026-05-23)#138
chore: sync FPF spec from ailev/FPF (2026-05-23)#138github-actions[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![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: 2c158e93f3
ℹ️ 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 rename removes route:boundary-unpacking-claim-routing from the generated route set, but runtime logic still hard-codes that ID in scoreAdoptionRouteIntent (src/runtime/query-helpers.ts) and in routeAcceptanceCheck/routeNextMove (src/runtime/answer-projector.ts). After this sync, those route-specific boosts and answer templates no longer trigger for boundary-review queries, which can change ranking and degrade guidance. Add an old→new route-ID alias (or update all hard-coded references in the same change) to avoid this regression.
Useful? React with 👍 / 👎.
| "slug": "admissible-comparison-candidate-pool-policy-selection-and-selected-set-publication", | ||
| "title": "Admissible comparison, candidate-pool policy, selection, and selected-set publication", | ||
| "staticPath": "/generated/routes/route_admissible-comparison-candidate-pool-policy-selection-and-selected-set-publication" |
There was a problem hiding this comment.
This sync replaces earlier comparison route IDs with new slugs, but user-facing docs still reference removed IDs (for example route:lawful-comparison-pool-selection-selected-set-publication in docs/start-here.md). Since explicit route selectors only work for IDs present in the registry/snapshot, those documented selectors now fail to resolve. Please provide backward-compatible aliases for renamed route IDs or update all documented selectors atomically with this data refresh.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
chore/sync-fpf-04dd733f
branch
from
2c158e9 to
68fb8df
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 68fb8df9cb
ℹ️ 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.
The route registry now removes route:boundary-unpacking-claim-routing and replaces it with route:boundary-unpacking-and-claim-decomposition, but user docs still instruct the old selector in docs/work-packets.md:50 and docs/mcp-recipes.md:98; because route lookup is exact by slug (ROUTE_BY_SLUG in src/docs/search-hooks.ts:66-67, matched at :114-116), those documented commands no longer resolve to a canonical route page after this sync. Please add an alias for the old slug or update these docs in the same change so guided review flows keep working.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
chore/sync-fpf-04dd733f
branch
from
68fb8df to
65277ff
Compare
Auto-detected new commit on
ailev/FPFmain.04dd733fb18b66d3a640d11758e0af22ea253fd8CI 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.