feat(helios): land benchmark-provenance + harness-preservation + toolchain-refresh shard - #628
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d857e20b79
ℹ️ 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".
| @@ -1,251 +0,0 @@ | |||
| name: CI | |||
There was a problem hiding this comment.
Restore the generic CI workflow
With .github/workflows/ci.yml emptied, pushes and PRs no longer define the generic lint/test/security jobs that used to run here, so regressions are skipped instead of failing and any branch protection expecting ci / lint or ci / test will see a missing check. Restore this fail-hard workflow or replace it with an equivalent gate in the same change.
AGENTS.md reference: AGENTS.md:L143-L144
Useful? React with 👍 / 👎.
| @@ -1,515 +0,0 @@ | |||
| #!/usr/bin/env python3 | |||
There was a problem hiding this comment.
Restore the harness runner CLI
Because harness/scripts/run-harness.py is now zero bytes, documented invocations such as python3 harness/scripts/run-harness.py discover/run/validate and the importable wrapper in harness/src/harness/scripts/run_harness.py exit successfully without parsing arguments or writing the requested artifacts. That silently breaks benchmark/provenance runs and leaves downstream consumers with missing or stale evidence.
Useful? React with 👍 / 👎.
| @@ -1,37 +0,0 @@ | |||
| { | |||
There was a problem hiding this comment.
Restore the Node package manifests
The release workflow still runs root pnpm install --frozen-lockfile before staging npm packages (.github/workflows/rust-release.yml:1200-1203), and pnpm install --help confirms it installs the current project's dependencies; with package.json and pnpm-lock.yaml zeroed, pnpm aborts immediately on Invalid package.json in package.json. This blocks release packaging and also breaks local root pnpm run tooling until the manifests are restored.
Useful? React with 👍 / 👎.
Code Review SummaryStatus: No Inline Issues Found | Recommendation: Review Complete (PR already merged) Overview
Files Reviewed (13 files)
Observations
Reviewed by step-3.7-flash · Input: 69.1K · Output: 3.8K · Cached: 190.7K |
PR #628 emptied .trunk/trunk.yaml (main currently has a 0-byte file), so Trunk Check has failed on main since. Restore the schema-0.1 config that validated GREEN on CI (run 31551719038): trunk plugin ref v1.11.0 (fixes taplo single-file download and ruff --output-format), pinned linter versions (actionlint, black, clippy 1.88.0, eslint, golangci-lint, mypy, prettier, ruff 0.16.2, rustfmt 1.88.0, shellcheck, taplo, yamllint), plus .trunk/.gitignore for the runtime dirs. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>



User description
Shards the unique work from 3 helios-cli branches onto current main:
CodeAnt-AI Description
Remove the Helios harness, benchmark evidence generation, and related automation
What Changed
Impact
✅ No phase-2 harness artifacts are generated✅ Helios harness commands are no longer available✅ Repository CI and lint automation are removed💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.