feat(tooling): soup hotfiles check in driver-rebuild --verify - #77
feat(tooling): soup hotfiles check in driver-rebuild --verify#77heavygee wants to merge 1 commit into
Conversation
Add hapi-soup-hotfiles-check.mjs (syncEngine rpcGateway call parity + codex route). Write ~/.config/hapi/driver-verify-stamp on successful verify. Document layer-collision repair pattern in driver-soup.md. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 466d8b4e56
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const calls = [...new Set([...syncEngine.matchAll(/this\.rpcGateway\.(\w+)\(/g)].map((m) => m[1]))] | ||
| const methods = new Set([...rpcGateway.matchAll(/^\s+async (\w+)\(/gm)].map((m) => m[1])) |
There was a problem hiding this comment.
Include generic calls in the parity scan
When syncEngine calls a generic gateway method with type arguments, as it already does with this.rpcGateway.callPiRpc<T>(...), this scan requires the method name to be followed immediately by ( and the method definition pattern has the same limitation for async callPiRpc<T = unknown>(...). In that collision case the new hot-file gate can still print OK while a generic rpcGateway call/method pair is missing from the advertised syncEngine ⊆ rpcGateway parity check.
Useful? React with 👍 / 👎.
Summary
hapi-soup-hotfiles-check.mjs(syncEngine→rpcGateway parity + codex route guard)~/.config/hapi/driver-verify-stampon successful--verifydriver-soup.mdTest plan
hapi-driver-rebuild --build-web --verifygreen on guestMade with Cursor