ONT-4c5 aprender extractor: capability-cells shape in pv lint (per paiml/infra#950)

[noahgift]

The spec is the ONT-4c5 row in paiml/infra docs/specifications/paiml-ontology.md, branch PMAT-921-v412, PR paiml/infra#950. Handed over by infra-83. The original aprender owner (aprender-6a) was terminated.

Needs:

• the capability-cells shape: the validator computes the set difference over ONT-4c1's ladder-green domain, restricted to the required rungs;
• pv lint --format json gains capability_cells.{domain,not_run} and pc_shapes["capability-cells"];
• contracts/ont-capability-cells-v1.yaml;
• tests/fixtures/ont/capability-cells-plant.yaml;
• a baseline of 14 cells: the 7 required q4km rungs × lambda and gx10.

Lands AFTER infra#950 merges. Note for #4045: under the new process the full ladder is nightly, so the ladder-green domain should come from the nightly receipts.

[noahgift]

triage 2026-09-23 (aprender-dd): kept in 0.70.0 and labelled ont-0.70. Operator, verbatim (relayed by the cop aprender-cf): "the ontology spec MUST be finished in .7". Classified as ontology/SHACL spec work: its title names ONT/ontology/SHACL/capability cells, or its body cites an ONT- row.

[noahgift]

triage (aprender-dd; cop aprender-cf ruling 2026-09-23): ONT-4c5 part 2/2, the pv-lint capability-cells shape. Part 1/2 is #3972 (the extractor + arming rule). One row, two halves, ONE owner takes both.

done_when (the single one for row ONT-4c5): #3972 is closed with its extractor + arming rule merged, AND this issue's pv-lint capability-cells shape is merged and passes on the extractor's output, with a planted-RED case.

[noahgift]

ONT-4c5 is code-complete on car #4429 (car/0.70.0 @ 93aa211e8). It is not yet on main. Checked by aprender-ea, 2026-09-25 ~20:30 Madrid. infra-83 confirmed they do not own this row; aprender-ea owns both halves now.

Evidence on the car head:

• cargo test -p aprender-contracts-cli --test ont4c5_capability_cells: 11 passed, 0 failed. The planted-RED cases pass:
  • every_not_run_required_cell_rejects_naming_exactly_that_cell: this is the arming rule, NotRun on a required cell gives RED.
  • disarming_capability_cells_turns_the_probe_red
  • a_deleted_current_release_row_rejects_naming_the_cell
  • an_empty_domain_declines_never_passes
• pv lint contracts --gate shapes --format json (pv 0.69.3 built from 93aa211): rc 0, verdict Pass.
  • armed_shapes = [capability-cells, ladder-measured, ladder-green, ont-shapes-v1].
  • pc_shapes["capability-cells"] = fired.
  • capability_cells.not_run = []; refused_labels = [].
• Files present on the car and absent on main: contracts/ont-capability-cells-v1.yaml and tests/fixtures/ont/capability-cells-plant.yaml. The code is in ontology/capability_cells.rs and lint/capability_cells_gate.rs, via be48bed (9c4264d, e2549bc).

Delta from the spec: the domain has 16 cells, not the 14 the issue named: 8 q4km rungs × {lambda, gx10}, with v_star 0.69.1. The ladder gained a rung after the spec was written. The gate derives the domain from the ladder, so the gate is not wrong. The row text in infra should say 16.

Remaining for done_when: car #4429 merges to main. #4429 lists these issues under Tickets:, which is not a closing keyword, so they will not close themselves. aprender-ea will close #3972 and #4047 when the car merges.