2026-05-01-gpt-5.5-necrobinder-run14

Summary

The Necrobinder run reached the Act 1 boss, Vantom, after stabilizing through two rest sites, one elite kill against Bygone Effigy, and several events. The deck had strong Osty attack cards, Bone Shards+, Deathbringer, and Letter Opener, but entered Vantom at only 42/66 HP with limited sustained block; Vantom's Slippery x8, Dismember/status turns, and scaling Strength outlasted the deck, and the run died on floor 17 after a 21-damage weakened attack with only 5 block available.

Bridge findings

• Invalid map command recovered: an attempted SelectMapNode {"col":4,"row":6} was sent from the floor 5 rewards screen before rewards were fully claimed; the bridge returned status=error with map point (4,6) is not currently travelable. This was an agent sequencing error, not a bridge defect.
• Card reward sub-screen sequencing error recovered: SelectCardOption {"cardIndex":0} was sent while still on the rewards list, before opening the card reward; the bridge returned status=error with no live NCardRewardSelectionScreen found in scene tree. I recovered by issuing SelectReward first, then selecting the card.
• PlayCard parameter error recovered: PlayCard was sent once with cardIndex instead of handIndex; the bridge returned status=error with PlayCard requires numeric 'handIndex'. I recovered by re-reading combat and using handIndex.
• Treasure relic parameter error recovered: SelectTreasureRelic was sent once with relicIndex instead of index; the bridge returned status=error with SelectTreasureRelic requires numeric 'index'. I recovered by re-reading treasure state and selecting with index:0.
• Helper script optional-field errors: tools/list-rest.ps1 and tools/list-grid.ps1 repeatedly printed useful state but also threw PropertyNotFoundException for optional fields such as smithCount, removableCardCount, title, description, and minSelection. These were tool-output issues, not game command failures.
• Potion refresh lag observed: Swift Potion in the Bygone Effigy fight returned ok and emptied the potion slot, but the drawn cards were not visible until after the next card action. This matched the documented potion refresh-lag pattern and did not stall the run.

Decision log highlights

• Neow choice took Arcane Scroll, then early rewards prioritized Osty/summon payoff cards: Lethality, Afterlife, Bone Shards, Flatten, Sic 'Em, Fear, Deathbringer, and Rattle.
• Took an early rest at 33/66 HP before continuing the Act 1 path, then later smithed Bone Shards+ at 59/66 because the next known node was an elite.
• Defeated Bygone Effigy with Deathbringer/Doom plus Bone Shards+ damage and block, leaving at 26/66 HP and gaining Letter Opener.
• In Slippery Bridge, paid 3 HP to avoid losing Flatten, then accepted Unleash removal after the reroll.
• Rested at the final rest site from 23/66 to 42/66 before Vantom instead of smithing.
• Against Vantom, prioritized stripping Slippery with small hits and applied Deathbringer for Doom and Weak, but the deck could not generate enough block during the Dismember cycle.

Notes for maintainers

The run environment exposed non-trial tools (webfetch, sub-agent/task, GitNexus skill tooling). I did not use web search, MemPalace, sub-agents, or GitNexus skills during gameplay, but the tools were visible in the environment.