Conversation
…l-LLM council on PRs - Add [workspace.lints.clippy] denying await_holding_lock, await_holding_refcell_ref, undocumented_unsafe_blocks, and missing_safety_doc; wire [lints] workspace = true into every crate, example, and the rust SDK. - scripts/pre-commit.sh (installed via `make install-hooks`): runs cargo fmt --check + clippy -D warnings on staged Rust and tsc --noEmit on staged sdk/ts, so master stays green without a CI round-trip. - CI: auto-promote the council-selftest to a real-LLM run on pull_request when a backend secret is present — ANTHROPIC_API_KEY (claude-code, preferred) else KIMI_API_KEY (pi-proxy). Fork PRs and no-secret repos stay on the free deterministic stub path. Bump the job timeout 10→20m and install the claude CLI only for real claude-code runs. - .gitignore: tmp/m2/, tmp/perf-vs/.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Repo-hygiene pass to keep
mastergreen by construction, plus turning the council self-test into a real dogfooding loop.[workspace.lints.clippy]deniesawait_holding_lock,await_holding_refcell_ref,undocumented_unsafe_blocks, andmissing_safety_doc; every crate/example/SDK opts in via[lints] workspace = true. Verified green:cargo clippy --workspace --all-targets -- -D warnings.scripts/pre-commit.sh, installed viamake install-hooks, runscargo fmt --check+clippy -D warningson staged Rust andtsc --noEmiton stagedsdk/ts— catches what the lints gate before a CI round-trip.aatxe-council-selftestnow auto-promotespull_requestruns to a real-LLM council when a backend secret is present —ANTHROPIC_API_KEY(claude-code, preferred; produced the published 0.857 critical-F1 baseline) elseKIMI_API_KEY(pi-proxy). Fork PRs and no-secret repos stay on the free deterministic stub path. Job timeout bumped 10→20m; theclaudeCLI is installed only for real claude-code runs..gitignore:tmp/m2/,tmp/perf-vs/.Notes
Reconstructed from a stale stash (
local M1 close-out changes before rebase). The stash's module-refactor and microVM hunks were already merged via #14/#15, so those resolved to master; the only salvaged piece was theinstall-hooksMakefile target (the hook script was otherwise orphaned). A strayautoresearch.jsonlbench-loop line was left out as unrelated.