crm: ContactModel's and SavedViewModel's journaling paths are executed by no test, and rung 7 is below its own coverage target

[Yaraslaut]

What is wrong

Two crm models' journaling paths are executed by no test at all, and
codecov.yml already records it as an open finding rather than a closed one:

ContactModel::attachActionLog and SavedViewModel::attachActionLog are
called by no test at all (both headers score 0/4), so those two models'
journaling paths are entirely unverified -- while AccountModel, LeadModel,
OpportunityModel and QuoteModel each have an explicit "journals its edits
against the attached identity" test. That is the same shape of gap ledger's
own first measurement turned up (a documented obligation nothing executed),
and it is open, not closed.

Four of six crm models have the test; two do not.

Why this is a defect report and not a coverage chore

The identical gap in a sibling rung was a real, user-visible defect. From the
same file, on lims:

the audit trail's own classifier, whose VerifyResult branch was dead because
verifications were being journaled under an empty entity key. That second
one was a real defect, not a coverage artifact: a sample's audit trail
silently omitted the second pair of eyes.

An attachActionLog that nothing calls is exactly the state lims was in before
that was found. The claim "this model journals its edits" is currently supported
by no executed line in either model.

The second half: the component is below its own target

crm is at 87.67% on master against target: 89% in codecov.yml — below,
and green, because every status is informational: true (morph#402).

codecov.yml is candid that crm's entry is less worked-through than its
neighbours':

Unlike those two, this entry does NOT yet carry a per-miss audit establishing
which of the 148 uncovered lines are unreachable-by-design rather than merely
untested.

So crm has 148 uncovered lines, no audit of them, and a target it does not meet.

Verification status: reproduced

• Codecov API, /components/?branch=master: crm → 87.67; codecov.yml on the
  same ref sets target: 89%.
• The 0/4 finding and the 148-line figure are quoted from codecov.yml's own
  comments, written when the component was added.

Not verified: that ContactModel::attachActionLog and
SavedViewModel::attachActionLog are still uncalled. The quoted measurement
was taken when rung 7 entered the report and I did not re-run it. Confirming or
refuting that is step one, and a refutation means codecov.yml's comment needs
correcting — itself worth doing.

What would close this

1. ContactModel and SavedViewModel each gain the "journals its edits against
   the attached identity" test its four sibling models already have, and each
   test fails without attachActionLog being called — proving the path is
   verified rather than merely reached.
2. Whatever those tests turn up is reported. If either model journals under a
   wrong or empty key, as lims did, that is the finding and it is filed
   separately rather than quietly fixed inside this ticket.
3. crm reaches its stated 89%, and the per-miss audit codecov.yml says is
   absent is written — each of the remaining uncovered lines classified as
   untested or unreachable-by-design, with reasons.

Not closable by calling attachActionLog from a test that asserts nothing
about what it wrote.

[Yaraslaut]

Acceptance reframed: kill named survivors, not reach a percentage

Recording a change of direction rather than editing the text above.

The first framework mutation run (morph#405) scored 64.06% against a library
already measuring 95.69% lines and 91.19% branches. That ~30-point gap is between
executed and would be noticed if it were wrong — and a percentage target is
what produced a suite sitting on the wrong side of it.

So this ticket's coverage-percentage clause is superseded. The work is now driven
by scripts/mutation_survivors.json, which names the missing assertions directly:

• morph#431 — the 255 unasserted survivors in include/morph/core, starting
  with twenty sites where the server's reply(...) can be deleted and the suite
  still passes.
• morph#432 — the 46 in include/morph/forms, mostly boundary comparisons
  exercised only away from their boundaries.

This ticket's non-percentage clauses still stand on their own and are not
superseded — the specific defect it names, the audit it asks for, and any
reachability question it raises are unaffected.

Why the change. The round that produced the measurement added 3013 lines of
tooling under scripts/, cmake/, .github/ and codecov.yml, and 130 lines
under tests/ — of which exactly one was a new test case. Coverage did not
move a point. Sequencing every measurement ticket ahead of every test-writing
ticket is a planning error, and this is the correction: infrastructure is frozen
(morph#430 moved to Backlog) until the survivors are killed.

The guard that comes with it. Do not chase the number. A mutant killed by an
assertion written to kill that mutant, on a path nobody cares about, is worse
than a survivor — it is a test with no reason to exist. Each new test must be
justifiable from the behaviour, with the survivor as evidence the assertion was
missing. Classifying a survivor as equivalent with a stated reason is a valid
outcome; the run already found 11 such.