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

[Dexterity104]

Adds one miner bundle for the sn60__bitsec miner lane.

[carlos4s]

Thanks for the challenge! Your agent went up against the current king and came up just short this time, so I've closed this PR. Here's exactly how it played out:

Here's how you stacked up against the king's average over its last 7 challenges, in the order the crown is decided — reading top to bottom, you take the crown by clearly beating the king on a line — by more than that line's margin — without falling behind on a higher one:

#	Signal	You	King	Win margin
1	Project pass score projects solved on a 2-of-3 majority	0% (0/7)	4%	>14.3% ← decided here
2	Projects passed projects with at least one passing run	0	0.3	>1
3	True positives real bugs found out of bugs planted	0/28	2.1	>2
4	Fewer invalid runs runs that errored out — fewer is better	0	3	>2
5	Precision how many of your findings were real	0.0%	53.8%	>5%
6	F1 score overall balance of precision and detection	0.0%	12.3%	>5%

How the crown is decided: read the lines top to bottom. On each line — if you're behind the king, the king keeps the crown and you can't make it up on a lower line; if you clearly beat the king (by more than that line's margin) you take the crown; if you're close (within the margin), that line is a tie and it moves to the next one. So to take the throne you have to clearly beat the king on some line (pass score first) without falling behind on a higher one. This stops a single lucky run from flipping the crown.

(The king's numbers are averaged over its whole reign — 7 challenges — since that's what it's judged on, so beating it on a single run isn't enough.)

So it came down to project pass score (tier 1) — that's where you fell behind the king, and since you can't make up a deficit on a lower line, the king kept the crown. To take it you'd need to stay even with the king (within the margin) down to a line where you clearly beat it.

Tweak your agent and open a fresh PR whenever you're ready — you can absolutely take another run at the throne. 👑

[carlos4s]

Thanks for the challenge! Your agent went up against the current king and came up just short this time, so I've closed this PR. Here's exactly how it played out:

Here's how you stacked up against the king's average over its last 8 challenges, in the order the crown is decided — reading top to bottom, you take the crown by clearly beating the king on a line — by more than that line's margin — without falling behind on a higher one:

#	Signal	You	King	Win margin
1	Project pass score projects solved on a 2-of-3 majority	0% (0/7)	4%	>14.3% ← decided here
2	Projects passed projects with at least one passing run	0	0.2	>1
3	True positives real bugs found out of bugs planted	1/21	2	>2
4	Fewer invalid runs runs that errored out — fewer is better	0	3.1	>2
5	Precision how many of your findings were real	33.3%	51.2%	>5%
6	F1 score overall balance of precision and detection	8.3%	11.8%	>5%

How the crown is decided: read the lines top to bottom. On each line — if you're behind the king, the king keeps the crown and you can't make it up on a lower line; if you clearly beat the king (by more than that line's margin) you take the crown; if you're close (within the margin), that line is a tie and it moves to the next one. So to take the throne you have to clearly beat the king on some line (pass score first) without falling behind on a higher one. This stops a single lucky run from flipping the crown.

(The king's numbers are averaged over its whole reign — 8 challenges — since that's what it's judged on, so beating it on a single run isn't enough.)

So it came down to project pass score (tier 1) — that's where you fell behind the king, and since you can't make up a deficit on a lower line, the king kept the crown. To take it you'd need to stay even with the king (within the margin) down to a line where you clearly beat it.

Tweak your agent and open a fresh PR whenever you're ready — you can absolutely take another run at the throne. 👑

[carlos4s]

Thanks for the challenge! Your agent went up against the current king and came up just short this time, so I've closed this PR. Here's exactly how it played out:

Here's how you stacked up against the king's average over its last 9 challenges, in the order the crown is decided — reading top to bottom, you take the crown by clearly beating the king on a line — by more than that line's margin — without falling behind on a higher one:

#	Signal	You	King	Win margin
1	Project pass score projects solved on a 2-of-3 majority	0% (0/7)	3%	>14.3% ← decided here
2	Projects passed projects with at least one passing run	0	0.2	>1
3	True positives real bugs found out of bugs planted	0/32	1.8	>2
4	Fewer invalid runs runs that errored out — fewer is better	0	3.1	>2
5	Precision how many of your findings were real	0.0%	45.6%	>5%
6	F1 score overall balance of precision and detection	0.0%	10.5%	>5%

How the crown is decided: read the lines top to bottom. On each line — if you're behind the king, the king keeps the crown and you can't make it up on a lower line; if you clearly beat the king (by more than that line's margin) you take the crown; if you're close (within the margin), that line is a tie and it moves to the next one. So to take the throne you have to clearly beat the king on some line (pass score first) without falling behind on a higher one. This stops a single lucky run from flipping the crown.

(The king's numbers are averaged over its whole reign — 9 challenges — since that's what it's judged on, so beating it on a single run isn't enough.)

So it came down to project pass score (tier 1) — that's where you fell behind the king, and since you can't make up a deficit on a lower line, the king kept the crown. To take it you'd need to stay even with the king (within the margin) down to a line where you clearly beat it.

Tweak your agent and open a fresh PR whenever you're ready — you can absolutely take another run at the throne. 👑

[carlos4s]

Thanks for the challenge! Your agent went up against the current king and came up just short this time, so I've closed this PR. Here's exactly how it played out:

Here's how you stacked up against the king's average over its last 10 challenges, in the order the crown is decided — reading top to bottom, you take the crown by clearly beating the king on a line — by more than that line's margin — without falling behind on a higher one:

#	Signal	You	King	Win margin
1	Project pass score projects solved on a 2-of-3 majority	0% (0/7)	3%	>14.3% ← decided here
2	Projects passed projects with at least one passing run	0	0.2	>1
3	True positives real bugs found out of bugs planted	1/35	1.7	>2
4	Fewer invalid runs runs that errored out — fewer is better	3	2.9	>2
5	Precision how many of your findings were real	20.0%	43.0%	>5%
6	F1 score overall balance of precision and detection	5.0%	9.9%	>5%

How the crown is decided: read the lines top to bottom. On each line — if you're behind the king, the king keeps the crown and you can't make it up on a lower line; if you clearly beat the king (by more than that line's margin) you take the crown; if you're close (within the margin), that line is a tie and it moves to the next one. So to take the throne you have to clearly beat the king on some line (pass score first) without falling behind on a higher one. This stops a single lucky run from flipping the crown.

(The king's numbers are averaged over its whole reign — 10 challenges — since that's what it's judged on, so beating it on a single run isn't enough.)

So it came down to project pass score (tier 1) — that's where you fell behind the king, and since you can't make up a deficit on a lower line, the king kept the crown. To take it you'd need to stay even with the king (within the margin) down to a line where you clearly beat it.

Tweak your agent and open a fresh PR whenever you're ready — you can absolutely take another run at the throne. 👑

[carlos4s]

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

Submission: submissions/sn60__bitsec/miner/Dexterity104-20260724-01
Challenge run: pr-205

Here's how you stacked up against the king's average over its last 11 challenges, in the order the crown is decided — reading top to bottom, you take the crown by clearly beating the king on a line — by more than that line's margin — without falling behind on a higher one:

#	Signal	You	King	Win margin
1	Project pass score projects solved on a 2-of-3 majority	14% (1/7)	4%	>14.3%
2	Projects passed projects with at least one passing run	1	0.3	>1
3	True positives real bugs found out of bugs planted	2/17	1.7	>2
4	Fewer invalid runs runs that errored out — fewer is better	0	2.6	>2 ← decided here
5	Precision how many of your findings were real	33.3%	42.1%	>5%
6	F1 score overall balance of precision and detection	17.4%	10.6%	>5%

How the crown is decided: read the lines top to bottom. On each line — if you're behind the king, the king keeps the crown and you can't make it up on a lower line; if you clearly beat the king (by more than that line's margin) you take the crown; if you're close (within the margin), that line is a tie and it moves to the next one. So to take the throne you have to clearly beat the king on some line (pass score first) without falling behind on a higher one. This stops a single lucky run from flipping the crown.

(The king's numbers are averaged over its whole reign — 11 challenges — since that's what it's judged on, so beating it on a single run isn't enough.)

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

[carlos4s]

This promotion has been reverted. PR #205 was crowned king in error: model inference failed for this submission (the sealed inference key returned 400 Bad Request from the provider, so the agent never ran real LLM inference), and it was promoted only on non-LLM static-fallback findings by a promotion path that did not require successful inference. The king has been restored to the previous holder (bohdansolovie-20260723-08). No action is implied about the submission itself; it may be resubmitted once its inference key issue (unsupported model / bad request to the provider) is fixed.