feat: verification probes with CI-aware execution policy - #5
Conversation
Both were resolving through hoisting locally but fail on the runner's bun linker. CI now runs the same bun as development. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQy3ZJ5MyUxo4qjZwA93Na
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQy3ZJ5MyUxo4qjZwA93Na
Engines can now execute targeted probes (snippet evaluation, single- function checks) to verify findings, while the commands CI already runs are auto-detected from .github/workflows and declared off-limits — re-running suites the runner executes anyway is pure compute waste. Claude/kimi get Bash with deny rules for suites, builds, installs, writes, and history-mutating git; codex keeps its read-only sandbox. Also restores the TOC README from #2, which was stranded on feat/review-framework because #1 squash-merged before #2 landed, and ignores generated app artifacts at the root. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQy3ZJ5MyUxo4qjZwA93Na
101a91a to
4c134f8
Compare
|
Added a sixth engine while this was open: |
|
Seventh engine slot filled while open: |
Two things: **Action no longer needs npm.** `@kyora-sh/review` has zero runtime dependencies, so the action now runs the CLI source straight from its own checkout (`version: bundled`, the new default) — `uses: eliahilse/kyora/action@<ref>` pins the code version naturally, and publishing to npm becomes optional (still available via `version: <npm-version>` for anyone who wants it). This unblocks CI installs entirely: workflow file + secrets, nothing else. **Recovers the glm + qwen engines.** The #5 squash-merge landed before the last two engine commits reached the branch (same stranding as the README in #2), so main was missing them. Cherry-picked: `glm` (GLM-5.2, Z.ai coding plan via Claude Code) and `qwen` (qwen3.8-max-preview, Token Plan via Claude Code) — both live-validated earlier. Full panel on main after this: codex, claude, kimi, glm, grok, qwen. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01CQy3ZJ5MyUxo4qjZwA93Na --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Reviewers can now execute, without duplicating CI.
bun -e/node -esnippets, exercising a single function against an edge case, git inspection — to verify a suspicion before reporting it.kyora-reviewparses.github/workflows/*forrun:commands, classifies suites/builds/linters/type-checks, and injects them into every engine prompt as banned ("if a finding depends on their outcome, state the expectation instead"). Re-running what the runner already runs is pure compute waste.Bashallowed with deny rules (test runners,bun run/npm runscripts,tsc,turbo, installs,rm/mv,git push/commit/checkout/reset); codex keeps its read-only sandbox which already permits execution without writes; grok/qwen get the policy via prompt.Also restores the TOC README from #2 — it was stranded on
feat/review-frameworkbecause #1 squash-merged to main before #2's merge landed on the branch, so main still had the old short README.Includes #4 (branched from it) — merge #4 first and this diff collapses to the execution-policy changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CQy3ZJ5MyUxo4qjZwA93Na