docs(aiv): correct PACKET_c2_f82_*.md — Repository field and Class B SHA permalinks (W2/W3, c2-f82 aiv-audit)

[ImmortalDemonGod]

What

All three c2-f82 AIV packets have two metadata defects surfaced by .aiv/verdicts/c2-f82/aiv-audit.md:

W3 — Wrong Repository field: All three packets (PACKET_c2_f82_impl.md, PACKET_c2_f82_tests.md, PACKET_c2_f82_crv.md) read Repository | github.com/ImmortalDemonGod/aiv-protocol. The correct value is github.com/ImmortalDemonGod/flashcore. Cosmetic template artifact that could mislead an auditor resolving the repo root.

W2 — Class B bare path#Lline references: The Class B scope inventories use bare path#Lline anchors instead of SHA-bound permalink URLs. Per spec B-002 this is WARN at R0–R1 (non-blocking), but reduces traceability.

Why deferred

Both were flagged as WARN-level (non-blocking) in .aiv/verdicts/c2-f82/aiv-audit.md. The load-bearing content checks passed and did not block merge. The aiv-audit provided complete remediation data:

• W3: change Repository to github.com/ImmortalDemonGod/flashcore in all three packets
• W2: replace bare anchors with SHA-bound permalinks; canonical form from aiv-audit harvested evidence: https://github.com/ImmortalDemonGod/flashcore/blob/c61f43182db1721ce2a34c25e81f204dc985d6a3/flashcore/cli/review_ui.py#L138-L148 (substitute per-stage packet's own head_sha for each file)

Acceptance criteria

• Repository field in all three packets reads github.com/ImmortalDemonGod/flashcore
• Class B scope inventory entries use SHA-pinned GitHub permalink URLs per the harvested evidence in .aiv/verdicts/c2-f82/aiv-audit.md
• aiv check --strict on corrected packets produces 0 E016 warnings (W2) and the corrected Repository field (W3)
• Corrections committed as docs(aiv): correct packet metadata — Repository field and Class B SHA permalinks [c2-f82 W2/W3]