feat(sn60): Dexterity104-20260728-01 concurrent breadth-first miner

[Dexterity104]

Adds one miner bundle for the sn60__bitsec miner lane.

[carlos4s]

I closed this PR because it failed the pre-scoring execution screener.

Your PR passed intake earlier, but before scoring I run the candidate once on a real benchmark project to make sure it can execute and return valid report JSON.

Screener project: sherlock_oku_2024_12

Reason:

• SN60 screening execution did not complete successfully: sealed-room run rejected: room run failed: room HTTP 500: {"error":"cp agent in failed: Error response from daemon: container rootfs is marked read-only\n","where":"Traceback (most recent call last):\n File "/app/room/server.py", line 133, in run\n return _run(raw)\n ^^^^^^^^^\n File "/app/room/server.py", line 196, in _run\n result = PROFILE.run(\n ^^^^^^^^^^^^\n File "/app/tee_profile.py", line 66, in run\n retur
• SN60 screening report must be a JSON object.

This candidate did not reach the challenge scoring, so this is marked kata:invalid rather than kata:losing.

[carlos4s]

Thanks for the PR. I’m pausing this one before it enters a challenge.

This is not a screening rejection and it is not about your agent's logic. I just could not confirm the current head commit passed intake screening — usually a new commit landed, an intake webhook was missed, or a transient or rebase error occurred.

What I saw:

• This PR has kata:pending, but the current head commit has not passed intake screening. This usually means new commits were pushed after screening, or an intake webhook was missed. Re-run /kata review before the PR can enter a competition challenge.

What to do: make sure the PR is rebased onto the latest default branch, then re-run /kata review. No changes to your agent are required for this.

Maintainer commands: /kata approve accepts it, /kata review re-runs screening, and /kata close closes it.
You can also push an update and the checks will run again.