docs(isa): mark S05 findings fixed upstream

[dmitrii-f-t27]

The pinned S05 specs still describe revision 976df517. Their new comment blocks identify which findings gHashTag/trinity#1250 fixed at e7919fdc, while preserving the pin, all findings and every executable rule. This implements the Queen-runnable scope of #5614; the Python replay model and JSON vectors remain unchanged.

Closes #5614

Specs: specs/isa/tri27_machine.t27 and specs/isa/tri27_bytecode.t27.
Report: docs/reports/2026-10-10-tri27-fixed-findings-5614.md.

Verification: machine 10/10 and bytecode 6/6 in Zig and native --check, four invariants each, no vacuous tests; zero discarded tokens; ordinary unforced seals verify all hashes. Comment/blank-line-stripped source and all four generated backend hashes are unchanged from master. No replay, hardware or inference update is claimed.

[dmitrii-f-t27]

Superseded by #8876.

Both PRs close #5614 and change the same two specs (specs/isa/tri27_machine.t27, specs/isa/tri27_bytecode.t27) and their seals. #8876 covers every note in this PR and adds executable constants, rules and tests for them:

• Machine: CALL pushes pc + 1, the loader packs one word per four-byte unit at byte 12 with pc 3, SACR keeps its mode in the immediate form, and the 3^9 label is correct. This PR lists them as findings 13, 14 and 15 (one-based). isa: S05 TRI-27 specs state the emulator fixed in gHashTag/trinity#1250 (Closes #5614) #8876 lists them as FIXED_FINDINGS = [12, 13, 14] (zero-based) plus MODULUS_NOTE. It also keeps the CALL stack guard open.
• Bytecode: the twelve-byte header agreement, the CONSTANTS id/count/payload layout and the placement at byte 12 with pc 3. This PR lists them as findings 7 and 8. isa: S05 TRI-27 specs state the emulator fixed in gHashTag/trinity#1250 (Closes #5614) #8876 lists them in FIXED_FINDINGS = [1, 3, 6, 7] with test vectors.

The only file unique to this PR is docs/reports/2026-10-10-tri27-fixed-findings-5614.md. It is a local work log. It points to paths on my machine and describes a comment-only diff, which is not true for #8876. So I do not carry it over.

This PR now has a merge conflict with master. #8876 is mergeable, and its required checks are green on head b05f8e088. Closing this one without merging.

Dmitrii Fedorov (@dmitrii-f-t27)