docs: repoint the 8 surviving src/abi/*.idr references and drop the LOC drift surface

[hyperpolymath]

What this is

033193c (#821) deleted the six duplicated src/abi/*.idr modules. Its title
says it "repointed every reference"; it did not. Eight references to the deleted
files survived on main. This PR closes that gap and corrects what the
references were saying.

Acceptance test, measured both sides:

git grep -nE 'src/abi/[A-Za-z]+\.idr' -- . ':!data/'

	hits
origin/main @ 0aa8972	8
this branch	1

The one remaining hit is test/unified-api-adapter-contract_test.exs:11, which
names the dead path in the past tense as a comment explaining why the guard
was repointed in #120. That is history and is correct.

What is deliberately not touched

• Every directory-level src/abi/ reference stays. The directory legitimately
  survives — it holds hypatia-abi.ipkg, hypatia-abi-gen.ipkg and a README.
  verify-proofs.yml's src/abi/** paths filter is therefore still correct, and
  no workflow file is modified by this PR.
• data/verisim/** telemetry, which records events about a different repo and
  names files that never existed in hypatia. Rewriting event records would falsify
  them.
• The past-tense sites in docs/DEBT-REGISTER.adoc, test/zig_ffi_smoke_test.exs
  and docs/proofs/HANDOVER-neural-convergence.adoc.

The four files

ffi/zig/src/main.zig:4 pointed at src/abi/Foreign.idr — wrong in two
ways, since no file of that name has ever existed under either directory.
Repointed to src/Hypatia/ABI/FFI.idr, where FFIFunction and
ffiReturnsApiResponse actually live.

verification/PROOF-STATUS.adoc — the six ABI rows repointed to
src/Hypatia/ABI/. Each content claim was re-verified against the live module
before being carried across, rather than relocated blind:

Row	Claim	Verdict
Types.idr	"Confidence refined type"	true — {auto prf : So (value >= 0.0 && value <= 1.0)}
Types.idr	"Severity ordering"	FALSE — replaced
RuleEngine.idr	all six properties	true — Sections 1, 2, 4, 5, 7, 8
GraphQL.idr / GRPC.idr / REST.idr / FFI.idr	as written	true

The Types.idr "Severity ordering" claim is contradicted by that module's own
comment at lines 157-159: "has never existed in this module; connectorCount
is the real pin." Replaced with the property the module does prove,
connectorCount : length allConnectors = 16.

The hand-written LOC column is deleted from both inventory tables, with the
two derived total lines and the duplicate "File Locations" file tree. Every one
of the twenty figures was wrong:

File	documented	actual
GRPC.idr	~150	64
GraphQL.idr	~200	93
REST.idr	~150	95
FFI.idr	~100	66
Types.idr	140	250
VerisimdbConnector.idr	~110	175
KinGate.tla	~130	198
…and 13 more

Nothing consumes them, so they are pure drift surface. A NOTE in the document
records why the column is gone, so it is not helpfully restored.

verification/README.adoc had two real bugs: a link to PROOF-STATUS.md,
which does not exist, and a build line cd src/abi && idris2 --build hypatia-verify.ipkg that is wrong in both directory and mechanism. Replaced
with what CI actually runs — the per-file idris2 --check loop at
.github/workflows/verify-proofs.yml:100-107 — plus the three real packages.

.machine_readable/INTENT.contractile:45 repointed. Checked first that
SD022 in lib/rules/structural_drift.ex tests directory existence only and
never a content claim, so this edit has no consumer and breaks no test.

On #816

This advances #816 on ACs 1-3 and does not close it.

• AC1 asked for LOC re-derived from wc -l. Superseded: measuring proved
  every figure wrong, so the column is deleted rather than re-derived. Rationale
  in a comment on the issue.
• AC2 (correct paths) and AC3 (name connectorCount = Refl) land here.
• AC4 demands a live CI check and AC5 a mutant proving it red. Neither can
  be satisfied in this PR — see the issue comment for the measurement.

Related findings, filed as issues rather than folded in

Per the standing rule that a new finding is an issue, not a merge blocker:

1. hypatia's entire ExUnit suite is dead in CI — the repo's only mix test sits
   in a job whose needs: points at a permanently failing one, so it resolves to
   skipped.
2. tests.yml is startup_failure on main, and governance / Actions lockfile verify is red there, both since the Dependabot pin bumps in chore(deps): bump the actions group across 1 directory with 4 updates #830.

🤖 Generated with Claude Code

https://claude.ai/code/session_0113HQM9LVGkNCzU1WwkJZSV

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e0a033df-5911-4a38-ac6b-775a5751e047

📥 Commits

Reviewing files that changed from the base of the PR and between 0aa8972 and 0eefa53.

📒 Files selected for processing (4)

• .machine_readable/INTENT.contractile
• ffi/zig/src/main.zig
• verification/PROOF-STATUS.adoc
• verification/README.adoc

 _________________________________________________________________________________________________________________________
< It is better to have 100 functions operate on one data structure than 10 functions on 10 data structures. - Alan Perlis >
 -------------------------------------------------------------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}