fix(POLICY-ISSUE-INTAKE): a frozen-evidence quote may rebase a relative link, and nothing else

[phantomic12]

fix(POLICY-ISSUE-INTAKE): a frozen-evidence quote may rebase a relative link, and nothing else

An _intake record's Problem must quote its frozen archive line byte for
byte, and check-agent-record's check_links requires every link in a
record to resolve from the record's OWN directory. Those two demands
cannot both hold on one string. The archive lives at
.agents/completed/issue-index.md, one level under .agents, so a link
to a spec reads ../specs/x.md there; the record that QUOTES the row
lives at .agents/issues//, two levels down, so the same link
must read ../../specs/x.md from there. e3539d9 re-pointed the
ISSUE-GH-1033 quote to the record-relative spelling to clear the
dangling link, which is correct for its own gate and broke the byte
comparison: first divergence at column 2191 of archive line 350, the
archive line 2237 characters against 2240 in the evidence.

The comparison now resolves each side's relative link targets to the
file they denote, and only then. Byte equality is still tried first
and still answers an unmoved archive, so no record that passes today
changes how it passes. When the bytes do differ, the rebase admits
exactly the spelling a MOVE forces and nothing else: remote and
root-absolute targets are never rewritten, so a swapped URL still
fails byte for byte, and a rebase to a different file, a different
fragment, a changed title, a changed kind, a changed row cell, or a
different line all still fail. The resolution is scoped to the
record's own directory, which validate_issue_record derives from the
owner directory it already checked, and valid_intake_archive_evidence
keeps byte-only behaviour for a caller that cannot say where the quote
lives rather than guessing a base.

MEASURED over the 831 records that carry a Frozen archive evidence
block: 350 are byte-equal, 438 differ from their cited line ONLY by a
relative link rebase, and 43 cite a line the archive no longer has --
24 past its 886 lines, since 2e84a07 deleted the file and e3539d9
re-added a shorter one, and 19 naming a row that moved. This change
does not extend the check to row-owned records, so it greens nothing
on its own; it removes the contradiction that made those 438
unfixable-as-written, and it is the prerequisite for enforcing the
block outside _intake at all. The 43 stale citations are a separate
question, because their quotes are historically true and the archive
is not frozen in the way the name claims.

On the ISSUE-GH-1033 record specifically: byte-equal False, modulo
link rebase True, and the record validates once the check is
reachable for a row-owned quote. Its own state is UNKNOWN with
Availability METADATA_ONLY, so the evidence branch that runs this
comparison is the _intake one and does not apply to it today; that
is precisely why the drift went unnoticed, and why this is filed as
the prerequisite rather than as a green gate.

TESTS: six cases in tests/scripts/test_issue_records.py. One accepts a
quote whose only difference is a rebase that resolves to the same
file; four hold the rejections (a rebase to a different file, a
different fragment, a remote target, a root-absolute target) so the
relaxation cannot widen; one holds that a caller with no record base
still gets byte equality only. RED-first proven: the two acceptance
cases fail against the pristine checker (one on the comparison, one on
the new argument) and pass with it. test_issue_records 114 passed,
test_agent_issue_index 13 passed, check-agent-record rc=0
(ENGINE=179 MODEL=384 QUANT=87 KERNEL=60 BACKEND=90), invalid records
4 before and 4 after against the committed archive.

RELATES TO #3346 and #3347, which see the same contradiction from the
two gate ends: agent-issue-index --check and check-agent-record's
check_links. This PR is the prerequisite half of that pair. #3347
makes each checker report every failure in one run instead of
stopping at the first; this one makes the two demands on a single
string satisfiable at all. Neither grews looser, and neither turns a
red gate green on its own.

SCOPE, deliberately excluded. The 43 stale citations are a maintainer
decision, not a checker change: their quotes are historically true,
and the archive is not frozen in the way the name claims, since
2e84a07 deleted the file and e3539d9 re-added a shorter one.
Whether to re-anchor, re-quote, or retire those records is a question
about record semantics. Also excluded: extending this check beyond
_intake to row-owned records. That would newly enforce 481 records
(438 rebased, 43 stale) and deserves its own PR with its own
red-first run against the full corpus.

FOR REVIEW. The relaxation is reachable only where a relative link's
spelling is the sole difference, remote and root-absolute targets are
never rewritten, and byte equality is still attempted first, so no
record that passes today changes how it passes. The four rejections
in TestMigrationIntake are where a stricter rule than resolves-to-the-
same-file would have to be argued, and the no-record-base case is
where a caller that cannot say where the quote lives is refused
rather than guessed at.

ISSUE-LOCAL-01M3NH23E78PEXCJF4HW1XHQQ3

FOLLOWING_AGENTS_PROTOCOL

Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:codebuff/buffy [freebuff]

[mudler-agent]

Closing as superseded by #3353. The complete reviewed stack merged there, and its commit 957be3a07a05617a082a2f217371b9b5cac5c89d has the same stable patch ID as this PR.