VERIFICATION COVERAGE

Find the evidence gap before running the next test

This page does not treat published content as verified by default. It maps the Phase 4B symptom paths to Errors, APIs, Object Hubs, Guides, and Tools, then calculates current coverage through the existing accepted Verification boundary.

Current rule

Evidence strength and coverage completeness stay separate. Without accepted Console or live multi-tick evidence, a path remains unverified; documentation review, offline simulation, or a database row cannot promote it on their own.

NEXT CAPTURE QUEUE

Turn evidence gaps into the next five capture jobs

This queue is derived from the same accepted + Markdown-accepted Runtime Evidence boundary used by Coverage. Target-covered paths drop out automatically. Within each priority, Partial paths come first, then Unverified paths keep registry order. The queue prioritizes capture work only; it never creates or accepts Evidence.

10open capture targets
#1
P0

Spawn will not spawn

Partial
TargetConsoleCurrent4 accepted record(s)Still missingERR_BUSY · ERR_RCL_NOT_ENOUGH

Capture nextPrioritize ERR_NOT_ENOUGH_RESOURCES, ERR_NAME_EXISTS, ERR_BUSY, and one OK path without generalizing to long-term queue behavior.

#2
P0

Controller downgrade pressure

Partial
TargetLive multi-tickCurrent2 accepted record(s)Still missingtarget evidence level · ERR_NOT_ENOUGH_RESOURCES · ERR_INVALID_TARGET

Capture nextRecord upgradeController() results, Upgrader Energy, Controller progress, ticksToDowngrade, and supply-side state across ticks.

#3
P0

Creep not moving

Unverified
TargetLive multi-tickCurrent0 accepted record(s)Still missingtarget evidence level · ERR_NO_PATH · ERR_TIRED · ERR_NOT_IN_RANGE

Capture nextCapture the real moveTo() result, creep.fatigue, start/end positions, and at least one later tick.

#4
P0

Creep not harvesting

Unverified
TargetLive multi-tickCurrent0 accepted record(s)Still missingtarget evidence level · ERR_NOT_IN_RANGE · ERR_INVALID_TARGET · ERR_NOT_ENOUGH_RESOURCES

Capture nextRecord the harvest() result, target type, WORK parts, resource amount, and later-tick Store/Source changes.

#5
P0

Link not transferring Energy

Unverified
TargetLive multi-tickCurrent0 accepted record(s)Still missingtarget evidence level · ERR_TIRED · ERR_NOT_ENOUGH_RESOURCES · ERR_FULL · ERR_INVALID_TARGET

Capture nextCapture sender/receiver Stores, cooldown, return code, and next-tick state instead of relying on a single screenshot.

VERIFICATION COVERAGE

Coverage is measured against accepted runtime evidence

The registry prioritizes what should be proved next. Current coverage is calculated from structured Runtime Evidence that survives the same accepted + Markdown-accepted public boundary as Diagnostic Center, then matched to each path by canonical API identity.

10planned diagnostic paths2paths with accepted evidence6structured accepted evidence records
P0

Creep not moving

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence · 0/3 return-code branches

Coverage goal

Cover moveTo(), fatigue, no-path, and range branches, then verify later-tick position or state changes.

Next evidence to capture

Capture the real moveTo() result, creep.fatigue, start/end positions, and at least one later tick.

P0

Creep not harvesting

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence · 0/3 return-code branches

Coverage goal

Cover harvest() target, range, WORK-part, and resource branches, then verify Store or Source state changes.

Next evidence to capture

Record the harvest() result, target type, WORK parts, resource amount, and later-tick Store/Source changes.

P0

Spawn will not spawn

Partial
Target evidenceConsole
Current accepted evidenceConsole · 3/5 return-code branches

Coverage goal

First make the high-frequency spawnCreep() return-code, dryRun, and real-call boundaries reproducible in Console evidence.

Next evidence to capture

Prioritize ERR_NOT_ENOUGH_RESOURCES, ERR_NAME_EXISTS, ERR_BUSY, and one OK path without generalizing to long-term queue behavior.

P0

Controller downgrade pressure

Partial
Target evidenceLive multi-tick
Current accepted evidenceConsole · 1/3 return-code branches

Coverage goal

Put the Controller, Upgrader, Link/hauling supply, and ticksToDowngrade into one multi-tick evidence chain.

Next evidence to capture

Record upgradeController() results, Upgrader Energy, Controller progress, ticksToDowngrade, and supply-side state across ticks.

P0

Market action failed

Unverified
Target evidenceConsole
Current accepted evidenceNo accepted runtime evidence · 0/2 return-code branches

Coverage goal

Use controlled Console cases to confirm argument, Credits, Terminal, and transaction-Energy boundaries without generalizing one trade into a market strategy claim.

Next evidence to capture

Prefer low-risk, reversible, or read-only checks; when a real transaction is required, verify only the smallest explicit case and record limitations.

P0

CPU usage too high

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence

Coverage goal

Use multi-tick CPU/bucket and hotspot measurements to prove the performance problem and the effect of changes instead of concluding from one tick.

Next evidence to capture

Record Game.cpu.getUsed() section measurements, bucket, workload size, and before/after comparisons across multiple ticks.

Primary error branches

No single return-code branch defines this path.

Primary API surfaces

Related object hubs

Useful tools

P0

Resources not moving

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence · 0/5 return-code branches

Coverage goal

Connect withdraw/pickup, movement, transfer, and source/carrier/destination Stores into one complete multi-tick logistics evidence chain.

Next evidence to capture

Store withdraw, pickup, moveTo, and transfer results separately and track source, Creep, and destination Stores across ticks to locate the broken logistics stage.

P0

Builder not building or repairing

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence · 0/4 return-code branches

Coverage goal

Cover build()/repair() results, WORK parts, Energy, target type, and later Construction Site progress or structure hits changes.

Next evidence to capture

Record build/repair results, Creep Energy, WORK parts, target starting state, and at least one later tick of progress or hits.

P0

Tower not attacking, healing, or repairing

Unverified
Target evidenceLive multi-tick
Current accepted evidenceNo accepted runtime evidence · 0/2 return-code branches

Coverage goal

Cover Tower attack/heal/repair results, Energy, targets, and later state; treat range as an output factor rather than a substitute for runtime evidence.

Next evidence to capture

Prefer controlled repair or heal cases with action result, Tower Energy, target hits, and a later tick; add attack evidence only when it occurs naturally and can be recorded clearly.