13 workspace Cargo.toml edits converting pinned crates.io
versions of renacer, entrenar, entrenar-lora, batuta, and
trueno-graph to `{ workspace = true }` aliases pointing at
the in-tree crates (aprender-profile, aprender-train,
aprender-orchestrate, aprender-graph).

Root cause: after APR-MONO Phase 2/3 consolidation, several
crates still pinned old crates.io sibling versions. Each
carried a transitive dep on an older `aprender` (0.14.1,
0.27.8), producing a diamond that broke
`cargo clippy -p aprender` with an ambiguous-package error.

Post-fix metadata:
  aprender: 1 package (workspace 0.31.2)
  renacer / entrenar / trueno-graph: 0 crates.io packages

Unblocks main-andon (required CI checks) and PRs #1008
(FALSIFY-SHIP-016 PARTIAL) and #1009 (FALSIFY-SHIP-009 PARTIAL).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(apr-mono): eliminate sibling-pin diamond dep (muda)

13 workspace Cargo.toml edits converting pinned crates.io
versions of renacer, entrenar, entrenar-lora, batuta, and
trueno-graph to `{ workspace = true }` aliases pointing at
the in-tree crates (aprender-profile, aprender-train,
aprender-orchestrate, aprender-graph).

Root cause: after APR-MONO Phase 2/3 consolidation, several
crates still pinned old crates.io sibling versions. Each
carried a transitive dep on an older `aprender` (0.14.1,
0.27.8), producing a diamond that broke
`cargo clippy -p aprender` with an ambiguous-package error.

Post-fix metadata:
  aprender: 1 package (workspace 0.31.2)
  renacer / entrenar / trueno-graph: 0 crates.io packages

Unblocks main-andon (required CI checks) and PRs #1008
(FALSIFY-SHIP-016 PARTIAL) and #1009 (FALSIFY-SHIP-009 PARTIAL).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(ci-lint): unblock workspace clippy exposed by sibling-alias activation

The sibling-alias MUDA fix in 3f38207 activates crates that were never
clippy-gated under main's red CI. This commit adds the minimum lint-unblock
changes needed for `cargo clippy --all-targets -- -D warnings` to pass.

Code fixes:
- aprender-compute GPU path (wgsl_forward, cached_matmul, dispatch, parallel):
  underscore-prefix unused vars, `.unwrap()` → `.expect()` with descriptive
  messages, collapsible_if, doc_lazy_continuation, allow map_entry, drop two
  bogus `contract_post_*!()` macro calls (type-mismatched, never compiled).
- aprender-graph/shortest_path.rs: add `#[must_use]` + doc on dijkstra_path,
  `.map_or(false, |&d| cost > d)` → `.is_some_and(|&d| cost > d)`.
- aprender-graph/pattern.rs: `mapping.iter()` → `mapping`.

Crate-level lint allows (pedantic lints carried over from pre-monorepo crates
— to be fixed per-lint in dedicated follow-up PRs):
- aprender-profile/src/lib.rs: 9 pedantic lints (renacer legacy).
- apr-cli/tests/*.rs (13 files): `disallowed_methods` etc for integration
  tests where `unwrap()` is idiomatic.
- apr-cli/examples/tool_calling_demo.rs: `disallowed_methods` for serde_json
  `json!` macro expansion.

Dead code (MUDA-aligned cleanup):
- Delete apr-cli/examples/probar_tui_testing.rs + federation_tui_demo.rs —
  both reference the removed `ratatui` crate and deleted `federation::tui`
  module.
- Drop matching `[[example]]` entries from apr-cli/Cargo.toml.

Verification:
  cargo clippy --all-targets -- -D warnings  # clean in 36s

Ported from closed PR #1010 (commit 4338cbf on fix/apr-mono-muda). Keeps
#1011's Cargo.toml changes intact; no conflicts with the MUDA fix commit.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…umns (Refs PMAT-680, PMAT-681)

The running "MODEL-1 coverage N/10" counter in amendments v2.24.0..v2.29.0
silently assumed AC-SHIP1-009 (apr-provenance `GATE-APR-PROV-004`
multi-bind) was live on main as the 1/10 baseline. On main `601c0740f`
that baseline is not live — `contracts/apr-provenance-v1.yaml` is still
v1.0.0 with 3 gates; the SHIP-009 multi-bind addition lives only in
open PR #1009 (commit `90598277a`, not a main ancestor).

This commit:
- Bumps spec **Version** 2.29.0 → 2.29.1 (correction, not new content).
- Inserts "v2.29.1 correction amendment (2026-04-23)" paragraph above
  the v2.21.0 amendment block, stating the corrected counts:
    MODEL-1 6/10 on main (not 7/10 as v2.29.0 claimed)
    MODEL-2 6/12 touched on main (not 10/12 as v2.23.x running claim)
- Adds "On-main status" column to §4.2 MODEL-1 AC table, mapping every
  AC-SHIP1-* row to one of {on main, PR #NNNN OPEN, stacked branch}.
- Adds "On-main status" column to §5.2 MODEL-2 AC table, mapping every
  AC-SHIP2-* row to one of {DISCHARGED on main, PARTIAL on main,
  PR #NNNN OPEN, blocked on task #132 Phase 3}.
- Retains prior amendment text unchanged under the correction to
  preserve audit history.

Five-Whys on the drift:
1. Why did the count say 7/10 when main holds 6/10? — Amendments
   v2.24.0..v2.29.0 computed N/10 as prior + 1 on every PARTIAL
   landed on a branch, not on ancestry check vs main.
2. Why didn't main-ancestry gate the count? — No automation bound
   spec claims to `git merge-base --is-ancestor`.
3. Why no automation? — Zero-Tolerance policy (§3 row #8, v2.16.0)
   was codified faster than the tooling that would enforce it.
4. Why did the assumed-ancestry drift accrete? — SHIP-009 PR #1009
   opened but review-stalled; every amendment after it was written
   against the expected (not actual) merge order.
5. Why no single-source-of-truth for AC status? — The spec itself
   is the source, and it's hand-edited. PMAT-683 adds the
   `cargo xtask audit-ship-two` CI gate that closes this loop.

Known residual drift:
- `bench/ship_007.rs:32` comment "MODEL-1 is now at 4/10 AC-SHIP1
  items touched (SHIP-008 + SHIP-009 + ...)" inherits the same
  bad assumption. Code comments are out of scope for this
  doc-only correction; leave a PMAT-follow-up for code-comment
  reconciliation once SHIP-009 PR #1009 lands.

Ticket closure: PMAT-680 (wrap-text count), PMAT-681 (on-main vs
in-PR columns).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>