chore: sync FPF spec from ailev/FPF (2026-05-17)#134
chore: sync FPF spec from ailev/FPF (2026-05-17)#134github-actions[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
chore/sync-fpf-46d5d585
branch
from
f3b8e30 to
25e6b7a
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: 25e6b7aa64
ℹ️ 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": "causal-use-counterfactual-support-repair", | ||
| "title": "Causal-use / counterfactual-support repair", | ||
| "staticPath": "/generated/routes/route_causal-use-counterfactual-support-repair" | ||
| "slug": "boundary-unpacking-and-claim-decomposition", |
There was a problem hiding this comment.
Changing the committed route slug here means the canonical ID is now route:boundary-unpacking-and-claim-decomposition, but the rest of the repo still hard-codes route:boundary-unpacking-claim-routing (for example src/runtime/query-helpers.ts only applies the boundary claim intent scorer to the old ID, and docs/start-here.md, docs/mcp-recipes.md, and several query/MCP tests still reference the old selector). In contexts where users ask about API/contract/protocol boundary unpacking or follow the docs' route: selector, the renamed route no longer receives the intended exact/intent handling, so route retrieval and tests drift from the published snapshot.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
chore/sync-fpf-46d5d585
branch
from
25e6b7a to
762f930
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 762f93018c
ℹ️ 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": "admissible-comparison-pool-selection-selected-set-publication", | ||
| "title": "Admissible comparison / pool / selection / selected-set publication", | ||
| "staticPath": "/generated/routes/route_admissible-comparison-pool-selection-selected-set-publication" | ||
| "slug": "admissible-comparison-candidate-pool-policy-selection-and-selected-set-publication", |
There was a problem hiding this comment.
With this registry update, the comparison route exposed by the current published snapshot is now route:admissible-comparison-candidate-pool-policy-selection-and-selected-set-publication / route:admissible-comparison-pool-selection-or-selected-set-publication, and route:lawful-comparison-pool-selection-selected-set-publication no longer appears in published/current/fpf-index/snapshot.json. I checked the repo references and docs/start-here.md:30 still tells users to copy the old route:lawful-comparison-pool-selection-selected-set-publication selector, so following the Start Here table now sends users to a missing route instead of the comparison route.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
chore/sync-fpf-46d5d585
branch
from
762f930 to
a99a320
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a99a320b68
ℹ️ 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": "causal-use-counterfactual-support-repair", | ||
| "title": "Causal-use / counterfactual-support repair", | ||
| "staticPath": "/generated/routes/route_causal-use-counterfactual-support-repair" | ||
| "slug": "boundary-unpacking-and-claim-decomposition", |
There was a problem hiding this comment.
Renaming the route slug here changes the canonical ID to route:boundary-unpacking-and-claim-decomposition, but src/runtime/answer-projector.ts still keys route-specific acceptance and next-move text on route:boundary-unpacking-claim-routing (see the switch cases around lines 186 and 204). After this sync, boundary-route answers fall through to the generic branch, so users no longer get the tailored boundary decomposition guidance that this route previously provided.
Useful? React with 👍 / 👎.
Auto-detected new commit on
ailev/FPFmain.46d5d58573f9941702403007cea0e6fc7a6de80bCI 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.