A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2715
New public Rust code meets rust-quality before the structure job does
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Put the rust-quality verdict (examples, behavioural tests and prose for every exported item) where an author meets it while writing — the fast local checks and the change's own proofs — instead of first in the 15-30 minute structure job.
- Why
- 2026-10-14: two implementations (I1501, I1995) passed their own crate tests, clippy, rustdoc and cases, and then failed the structure job's rust-quality gate: seven and thirteen exported items with no executable example, no behavioural test or two-word docs. Each cost a further 20-40 minute round (fix, derive, structure job again). The gate's command was known; nothing asked for it before the structure job.
- Now
- rust-quality runs only as a structure gate (`cargo run -- quality report --summary`). scripts/rust-check, the pre-commit hook and the documented proof list for a Rust change do not include it.
- Wanted
- scripts/rust-check runs the quality report over the changed crate by default (or a documented `--quality` that the documented proof list and the agent brief name), it finishes in under a minute on a warm build, and a change that adds an exported item without an example is refused there with the same finding the structure job would give.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A new exported item without an example is refused by the local rust check with the structure job's finding
- The documented proof list for a Rust change names it
- Validation
bin/majordomus plan validate- Evidence required
local_rust_check_runs_quality_case- Evidence present
local_rust_check_runs_quality_case
Scope
- Touches
scripts/rust-checkdocs/RUST.mddocs/INTEGRATION.md.ai/repo/workflowstest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- none
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-14
- Updated
- 2026-10-14T22:50:02Z
- Started
- 2026-10-14T22:49:53Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T22:50:02Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.