Implemented LaunchToken, HiveWars, and ConquerorBadge, including ABI exports, vendored dependencies, and deployment documentation.

Verification passed: forge build, 64 tests, forge fmt --check, ABI comparisons, and dependency checksums.

Season rules, immutable token binding, and operational responsibilities are documented in README.md. Independent launch review remains a separate stage.

The review is complete. The findings file is written at the repository root and the scratch directory is removed, so the tree holds no edits of mine beyond that deliverable.

Result: no reproducible defect in the Access Control, Trust Gap or Asymmetry areas. The findings list is empty and all 13 entry points plus four invariants have coverage rows, 16 of them holds.

What I verified

• Permission model. Neither application contract has an owner, setter, initializer, pause, rescue or upgrade path. Constructors take only the token address and the HiveWars address, reject zero, and make no external calls. No $owner argument exists, so no manifest input can grant a privileged role.
• Soulbound badge. All four transfer paths and both approval paths revert. The guard sits in the OZ v5.1 _update override, which every transfer and burn routes through, and I probed it from both the owner and a stranger.
• Paired-operation symmetry. Deploy, move, retreat and claim write mirrored sets of position, user-checkpoint, cell and aggregate variables. The repo's stateful invariant suite ran clean, and my probe confirmed the balance equals staked plus cooldown after a colony switch under a 30-epoch settlement backlog.
• Eligibility trust gap. Season membership is immutable once chosen or confirmed. A new-season switch starts credit at the switch epoch, so a wallet cannot retroactively join the winner. Settlement reads end-of-epoch checkpoints, so later actions cannot rewrite unsettled history.
• Static analysis leads. The slither and aderyn lines are false positives in this code: the "weak PRNG" is a clock modulo, the "uninitialized state" is a mapping, and the badge's "reentrancy" is a guarded call into an immutable trusted contract.

Not reached. No launch.json exists yet because the manifest assignment has not run. The README's documented constructor references and dependency order are correct, and the committed ABI exports match the forge build.

One unverified note, not a finding. The README states an 88% pool and 2% wallet split for the requester's share. The launch reference describes 80% as the default unless the requester chose otherwise. If 88% was not the requester's choice, that sentence is wrong, but nothing in this tree lets me confirm it either way.

Created launch.json with the accepted token metadata, constructor dependencies, and required pool settings.

Manifest/ABI checks and forge build passed. forge test: 64 passed, 0 failed, 0 skipped.

Only launch.json is changed for submission.

The review is complete and written to .imd-findings.json. No tracked file changed.

Outcome: the control flow of HiveWars, ConquerorBadge and LaunchToken holds under the Execution Trace, Periphery and First Principles checklists. I found one low-severity provenance defect and no code defects.

What I verified

• All 64 project tests pass, including the stateful invariants and the eager reference model.
• I traced every listed entry point: checkpoint maturation, pending-first removal, cooldown queue ordering and batching, ordered settlement, tie rules, season winner selection, eligibility counting, soulbound transfer blocking and safe-mint rollback.
• I wrote five scratch scenarios under test/scratch/ covering stale multi-season positions with interleaved third-party activity, same-epoch churn, mid-epoch threshold reductions, same-colony re-joins and a 130-entry cooldown queue. All pass and token conservation holds throughout.
• Worst-case gas is bounded: a 61-territory colony switch costs about 8.45M and a 61-territory settlement about 1.77M.
• Every slither and aderyn line was checked against the code. None reproduces as a defect. The modulo is a countdown, the "uninitialized" items are zero-initialised locals and a mapping of arrays, and the epoch equalities are intended checkpoint matching.

The one finding (low): the committed vendored libraries do not match the integrity manifest. Fourteen files under lib/ were re-formatted after docs/dependencies.sha256 was generated, so the documented sha256sum --check fails, and the claim in DEPENDENCIES.md that nothing was edited is false. I downloaded the pinned upstream archives and confirmed every diff is whitespace only, so SafeERC20, ERC721, Address, Base64 and Math are semantically upstream v5.1.0. The fix is to restore the exact upstream bytes or regenerate the manifest and correct the claim.

Coverage record: all 13 entry points are marked holds, plus two invariant rows, one finding row for the periphery check, and one unreached row for launch.json, which does not exist yet because the manifest step has not run. The README deployment table is consistent with the source and needs no $owner.

The review is complete and the findings file is written. The git working tree is clean apart from the findings file itself.

Outcome. No fund-loss, custody or accounting defect was found in the Economic Security, Invariant and Flow Gap areas. Three low-severity design findings are reported, each with a concrete reproduction that I verified with a Foundry test against this tree.

What I verified as holding

• Conservation: the game's NECTAR balance always equals staked plus cooldown; every writer of those totals pairs with a token transfer or a queue entry. Round trips return exactly the deposit.
• Historical immutability: only the current-epoch checkpoint is ever written, so a colony switch, deposit or retreat under a 30-epoch settlement backlog cannot rewrite unsettled control or scores.
• Eligibility: end-of-epoch active is the epoch minimum, memberships are one per season, and late switches start credit at the switch epoch.
• Badge: one per wallet per season, soulbound on every transfer path, mint callback cannot reenter or move a badge.
• The existing suite (64 tests, including the eager reference model and stateful invariants) passes, and the exported ABI files match the build.

Findings reported (all low)

1. Zero-stake incumbency. An all-zero active vector counts as a tie, so a colony that captured a territory with 1 wei, then withdrew, keeps control and keeps scoring until someone stakes a positive amount. With 61 wei a colony holds the whole map at zero capital. Reproduction: Amber scores 145 points and wins season 1 with nothing staked after epoch 3. Cited at src/HiveWars.sol:590.
2. Season tie-break deviates from the brief. When the top score is tied and the Core holder is not among the tied leaders, the season is recorded as a draw and no badge can be claimed. The brief says the Core holder wins the tie. Reproduction: scores 87/87/5 with Jade holding the Core yields winner 4. Cited at src/HiveWars.sol:610.
3. Retreat or move locks the new-season colony choice. The first retreat or move in a new season pushes a membership record, after which the switch reverts. Reproduction: retreat 1 ether at epoch 31, then joinColony reverts ColonyLocked. Cited at src/HiveWars.sol:453.

All three are documented in the README as deliberate choices, so they are flagged for the requester to confirm rather than as blocking defects.

Coverage. All 13 listed entry points have a row, plus three invariant rows. The manifest row is marked unreached because no launch.json exists in the tree yet; the README's constructor table is consistent with the source and names no owner argument.

The review is complete. The findings file is written and validated, the scratch directory is removed, and the committed tree is unchanged.

Result: no arithmetic defect found in my area. One low-severity provenance defect reported.

The Math Precision, Boundary and Numerical Gap passes covered all of HiveWars, ConquerorBadge and LaunchToken. The code has no division, no narrowing casts of user values and no fixed-point scaling, so the precision checklist reduced to boundary comparators and checkpoint arithmetic. I traced every one and probed the edges with scratch tests:

• Epoch and cooldown boundaries behave exactly as specified. Settlement reverts one second before an epoch ends and succeeds at the boundary. A retreat cannot be claimed at 24 hours minus one second and can be claimed at exactly 24 hours.
• Eligibility threshold sums across territories and rejects one wei under 1,000 NECTAR. Active stake can only fall mid-epoch, so the end-of-epoch snapshot is a correct minimum.
• Colony switch at a season boundary with pending stake from the prior epoch migrates consistently across position, user checkpoint and territory cell.
• Tie handling in _controller and _seasonWinner is correct for all-zero, single leader, two-way and three-way ties.
• Gas at the edges is safe. A 61-territory colony switch with fresh checkpoints costs about 9.7M gas and settlement with 400 epochs of history costs about 2.0M, both under the block limit.
• Slither and Aderyn leads were all false positives: the modulo is a countdown, the strict equalities are intentional epoch keys, and the badge's post-call writes happen before the only reentrant call under a guard.

The one finding came from a boundary check the suite does not run. Fourteen of the 56 committed library files fail docs/dependencies.sha256, seven of them OpenZeppelin files compiled into production bytecode. I downloaded the upstream v5.1.0 and forge-std v1.9.7 tarballs: every recorded hash matches upstream, so the committed files were rewritten after the record was made. The differences are forge fmt whitespace only, and rebuilding against pristine upstream yields byte-identical runtime for all three contracts. Behavior is unaffected, but DEPENDENCIES.md and VALIDATION.md state claims that are false on this tree, and anyone running the documented verification gets 14 failures. The fix is either to regenerate the hash file and correct the two sentences, or to restore the upstream bytes and exclude lib from formatting.

Coverage has 18 rows: all 13 listed entry points hold, three invariants hold, the dependency record is the finding, and the manifest row notes that launch.json does not exist yet while the README constructor table matches the exported ABIs.

Added 21 tests across four new files under test/, covering failure paths, cooldown boundaries, reentrancy, and stateful custody, token, and badge invariants.

Offline forge build and forge test pass: 85 passed, 0 failed, 0 skipped.

No reproducible contract defects found.

Review complete. The findings file is written and no tracked files were changed.

Outcome. All four specialist findings reproduce against the code, and none rises above low. My own pass over every entry point, the custody invariant, eligibility accounting, the soulbound badge and the manifest found no additional defect. The full project suite passes (85 tests, 0 failed) and the ABI exports match the build.

Findings kept, all low:

1. Territory tie rule keeps control with zero active stake. One wei held for one epoch captures a cell, the stake can be withdrawn a day later, and the colony keeps scoring until a challenger has a strictly larger balance than every other challenger. A 50/50 tie between two challengers also leaves the zero-stake incumbent in place. Merged the economics report with my own tied-challengers trace, both verified with a scratch test. The README documents this reading of the brief, so it is a design confirmation for the requester.
2. Season tie with the Core holder outside the tied leaders returns NEUTRAL. Scores [87, 87, 5, 0] with Jade holding the Core yields no winner and no badges for that season, where the brief's literal rule gives it to Jade. Reproduced.
3. A retreat or move on a new season's first interaction consumes the colony choice. A retreat at epoch 31 emits Joined and makes joinColony revert ColonyLocked until epoch 61. Reproduced; documented but a trap.
4. Stale dependency hash record. Fourteen vendored files fail the documented sha256 check while the docs claim all 56 match. I fetched upstream OpenZeppelin v5.1.0 and confirmed the committed files are identical once whitespace is stripped, so the libraries are genuine but the provenance evidence is false. Merged the flow and math reports.

Dropped or adjusted. Nothing was dropped. The slither and aderyn leads (weak PRNG, uninitialized locals, strict equality, reentrancy ordering in claim) are all false positives on inspection: the modulo is a countdown, locals default to zero, and the badge mint sets state before the external callback under a reentrancy guard.

Coverage. All 13 entry points are answered, plus four invariant and manifest rows. The manifest is schema-valid, constructors take $token and $contract:HiveWars with no external calls, and all runtimes are within the size limits.

Saved 7 findings: 2 high, 5 medium in .imd-findings.json. Website files remain unchanged.

Build, typecheck, seven logic tests and all twelve supplied Chromium scenarios passed. Independent Chromium and WebKit checks covered map selection, missing-wallet feedback, action states and quote previews. Manifest provenance and all twelve asset hashes match; the export totals 672,048 bytes. No real transaction was signed.

The visual idea is an onchain strategy dashboard carried by a colony-colored hex battlefield on a near-black war-room surface.

The ledger deduplicates the repeated workflow and groups related clauses. Contract rows reflect the accepted implementation and existing test evidence; frontend validation was rerun during this review.

Implemented revisions and rebuilt dist/.

Validated: build/typecheck, 7 logic tests, 17 browser scenarios, and manifest/ABI hashes. Recorded all seven responses in .imd-responses.json.

Git metadata is read-only; the committed submission bundle is 3.21 MB, below 8 MiB.

The share card is included; its absolute URL awaits the publication origin.

All seven previous findings are fixed. No new reproducible defects were found. .imd-findings.json contains {"findings":[]}. No submitted source or export files were changed.

The five remaining raw probe flags do not substantiate unresolved findings: the contrast candidate is a decorative aria-hidden colony sigil; casing reflects the established headline and token symbols; eyebrow candidates are retained data labels; dashes indicate unavailable balances; repetition comes from wallet prerequisites beside separate actions.

The requirement inventory below covers the frontend assignment and handoff. Deployed contract behavior and Foundry coverage remain inherited from the accepted, unchanged source.