Workers learn their budget is finite only when the wrap-up interrupt
arrives, which is too late: commands started minutes before exhaustion
die mid-flight, and their results are the ones lost. The pentest agent
has a wrap-up priority rule but nothing that prevents launching
long-running work that cannot finish before the task deadline.
Changes:
- worker seed: budget discipline block. Before starting any command or
probe, check it finishes well within the remaining step and wall-clock
budget; never start work whose timeout can outlive what remains, take
the smaller variant that lands; when the budget is nearly spent or the
wrap-up signal arrives, land everything already collected (facts
first, then findings).
- pentest seed: deadline contract bullet. Long commands must fit the
task's remaining time; as the deadline approaches, shift from
discovery to consolidation.
- agent/deadline_contract_seed_test.go guards the markers.
Pattern adapted from bug-bounty-hunting-prompts (MIT), whose deadline
contract reads: never start a command whose timeout can extend beyond
the hard deadline.
BaaRai
2629140b93