Skip to content

Promote agents to dev (agents-to-dev-2026-10-09) - #4

Merged
zah merged 4 commits into
devfrom
agents-to-dev-2026-10-09
Oct 9, 2026
Merged

zah merged 4 commits into
devfrom
agents-to-dev-2026-10-09

Conversation

@zah

@zah zah commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Stabilisation of agents cut at 6b79bd6. This is the first promotion since verno moved to the product branch model (dev mainline, agents landing branch).

Contents:

  • CI runs on dev and stable (push and pull request) instead of main, which has been retired.
  • The pre-commit configuration refuses added large files and added .ct recordings.
  • The report and payload documentation, the payload module and the harness scripts no longer cite documents readers of this repository cannot open. Comment and documentation changes only.

Verified locally on Linux x86_64, in the repository's dev shell: ./scripts/check-noir-pin.sh, cargo check --workspace --all-targets --locked, cargo test -p formal_verification --lib --locked, cargo fmt --all -- --check, and the pre-commit hooks over all files.
Not verified locally: the corpus job (it needs the venir toolchain; CI runs it).
Certificates: none (not a reprobuild test-certificate repository).

Zahary Karadjov and others added 4 commits October 4, 2026 10:16
Adopts the committed-binaries tier of the MCL Standard Hook Set
(mcl-standard-hooks) in the portable committed form,
per metacraft-dev-guidelines/policies/repo-requirements.md 4.3. Before this
commit this repository had neither a .pre-commit-config.yaml nor a
.git/hooks/pre-commit, so 4.3 was enforced here by nothing.

Both hooks act on files a commit ADDS (git diff --staged --diff-filter=A), so
adoption cannot retroactively fail anything already tracked. Verified here, in
both directions, before this commit: an added *.ct file and an added member of
a *.ct/ directory are each refused by name by ban-added-ct-recordings; an added
2 MiB file is refused by check-added-large-files as "exceeds 1024 KB"; and this
commit, an ordinary one, passes both.
verno now follows the product-repository branch model: `dev` is the
mainline, `stable` will carry releases, and `agents` is the agent landing
branch. `main` is being retired, so a push filter naming it would stop CI
from running on any branch without reporting anything.

Pull requests are filtered to the same two bases, so pull requests into
`agents` (which has no CI by policy) do not run the workflow either. The
documentation link to scripts/run-corpus.py now points at `dev`.
The machine-readable report documentation, the payload module and the
harness scripts cited documents that readers of this repository cannot
open, and labelled passages with internal work-item identifiers. Each
passage now states the rule it relies on directly.

The contract is still checked from both sides through
conformance/codetracer-payload/, which is the public, executable form of
it. No code or behaviour changes.
@zah
zah merged commit 792f9e0 into dev Oct 9, 2026
4 checks passed
@zah
zah deleted the agents-to-dev-2026-10-09 branch October 9, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant