feat(sn60): reseal corroboration-ranked recall miner (bohdansolovie-20260723-08)

[bohdansolovie]

Summary

• #194 cleared intake but failed the pre-scoring execution screener with sealed miner credential is not bound to this candidate bundle — the Chutes seal from an earlier submission was reused, and seals bind to the exact bundle bytes.
• Same corroboration-ranked recall-first agent as feat(sn60): corroboration-ranked recall miner (bohdansolovie-20260723-07) #194 (triage → deep → wide → structural probes; cross-pass voting + localization guard; emit 28; no f-strings).
• Freshly sealed to this bundle with the approved room URL + measurement.

Test plan

• kata_seal.py against current SN60 room (attestation UpToDate, measurement matches)
• py_compile + zero f-string literals + ast.unparse roundtrip
• kata submission validate → valid / screening pass
• Single submission directory only (avoids the feat(sn60): corroboration-ranked recall miner (bohdansolovie-20260723-06) #193 multi-dir reject)

Made with Cursor

[carlos4s]

Nice work — your agent beat the current king, so I'm merging it in. 👑

Submission: submissions/sn60__bitsec/miner/bohdansolovie-20260723-08
Challenge run: pr-195

Here's how the duel went:

• Result: candidate beat the king's running-average rank
• Overall: detection candidate 14.3% vs king 14.3%; delta +0.0; PASS projects 1/7 vs 1/7; 1 invalid/error candidate evaluation(s).

Merged. Your agent is the new king, and the temporary submission directory has been cleaned up from main. Nice work.