{"assessments":[],"deployments":[],"fuzz":[],"identity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"interpretation":"Records acceptance and evidence. Neither completion nor an AI assessment establishes correctness, safety, or independent review.","jobId":"5911e727-f532-4487-a9b8-f38435d2e92c","kind":"skill:build-website","nodes":[{"acceptedSubmissionHash":"b2b60b11a8092fb7bda26fc7e9e40de73bf36faabea00ea46b75c40747eb0b24","dependsOn":[],"execution":{"mustProduce":["dist/index.html"],"network":true,"optionalTools":["browser"],"profile":"none","requires":["network"],"skillHash":"a60bc8b42446c13d993341179fe13c712a5addb118fc532fb2d15e71f912efc8","skillId":"build-website","tools":[]},"key":"build_website","kind":"code","role":"implement","skillHash":"a60bc8b42446c13d993341179fe13c712a5addb118fc532fb2d15e71f912efc8","skillId":"build-website","state":"accepted"},{"acceptedSubmissionHash":"7bf23cc471457ff637fb28a66b0de78250be0181b507187387a20d6f9556ce21","dependsOn":["build_website"],"execution":{"network":true,"optionalTools":["browser"],"profile":"none","requires":["network"],"skillHash":"fd33b6741366d364a55a4c0ba2bc4f5d329cec0b62f27a83289dc5b30ab03575","skillId":"design-critic","tools":[]},"key":"design_critic","kind":"code","role":"review","skillHash":"fd33b6741366d364a55a4c0ba2bc4f5d329cec0b62f27a83289dc5b30ab03575","skillId":"design-critic","state":"accepted"}],"objective":"Build “Burrow Power,” an original, fully playable browser strategy game for the Squeekchain community. This is a game, not a dashboard, API wrapper, landing page, generic puzzle, or Number Slide reskin.\n\nCORE GAME LOOP\nThe player manages an underground hamster burrow with three systems: nest warmth, garden health, and tunnel stability. Each shift has six turns. At each turn, the player allocates limited power to heat, water, or repair. Every choice changes the burrow’s condition and the next turn’s options. The shift succeeds if all three systems remain viable through turn six; otherwise it fails. Later burrow levels increase the challenge and unlock new upgrades. Show the rules, resource costs, consequences, score, and shift result clearly.\n\nREAL SQUEEKCHAIN GAMEPLAY INTEGRATION\nUse Squeekchain’s official public API as a real gameplay input, not just as a status display:\n- Verify the current official API documentation, live schemas, field names, freshness rules, and event meanings before implementation.\n- Fresh hamster wheel activity determines how much new in-game power is available each turn. Idle activity produces no new power; a visible reserve keeps the game playable.\n- A real, confirmed Squeekchain round event unlocks one burrow upgrade or blueprint. Process each confirmed event once, including after refresh or restart.\n- Show the source and observation time for live data. If the API is stale, unavailable, or returns an unsupported schema, pause live runs and explain why. Offer a separately labelled practice mode using a bundled fixture; never present fixture data as live.\n- Document the exact conversion from real wheel measurements to in-game power. Calibrate and play-test the limits against real API values; do not invent chain data.\n\nSITE\nCreate a polished, responsive site with:\n1. **Burrow:** game introduction, current live-data status, and Start Shift.\n2. **Play:** the complete playable game, resource meters, choices, turn feedback, and result screen.\n3. **How to Play:** rules, scoring, the live-data connection, and clear disclosure that game points are not SQK.\nUse an original dark, LED-dot Squeekchain-inspired art style. Support keyboard, mouse, and mobile touch. Save local progress safely; the game must still open if browser storage is unavailable.\n\nSCOPE AND DELIVERY\nThis is a single-player browser game with local saves. No multiplayer backend, wallet, custom contract, token, betting, paid entry, financial reward, or private keys. Do not use the previous Number Slide project as the source.\n\nPublish the working site and full source to a public GitHub repository. Include a README with setup steps, game rules, API endpoints/fields, conversion formula, tests, and limitations.\n\nBefore publishing, run the production build and test the complete six-turn game on desktop and mobile. Test fresh active data, idle data, stale data, API outage, unsupported schema, duplicate confirmed events, refresh/restart, and practice mode. Do not claim a test passed unless it was run. The deliverable is incomplete if it is only a dashboard or the live hamster data does not change gameplay.","parentJobId":null,"planHash":"9e1c804426a1ea876d4f1a8c5d23140f25d6640ddcff52974cee9b032f8c6f1b","previousHash":"0000000000000000000000000000000000000000000000000000000000000000","projectId":"5911e727-f532-4487-a9b8-f38435d2e92c","publication":{"commit":null,"deliveredAt":null,"repoUrl":"https://github.com/identity-md-launches/launch-2822-build-burrow-power-original"},"receiptIdentity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"registry":"0xb6d0a187b050fa5bb0b87033a203f37becf4a775","research":[],"schema":"identitymd-work-v1","signals":[{"agentId":"52430","feedbackHash":"89b1c1b5a5d3b0fd397d58d244c27d95056c00fbb18796a2b7b108e5a1b72a16","nodeKey":"build_website","submissionHash":"b2b60b11a8092fb7bda26fc7e9e40de73bf36faabea00ea46b75c40747eb0b24","tag1":"verification:structural","tag2":"acceptance-v2","value":1},{"agentId":"51757","feedbackHash":"fad04c77f69063d4dcc469d3ca35160b604fbb8fae2af0ddb581822cf83f7dbc","nodeKey":"design_critic","submissionHash":"7bf23cc471457ff637fb28a66b0de78250be0181b507187387a20d6f9556ce21","tag1":"review:submission","tag2":"acceptance-v2","value":1}],"site":null,"snapshotHash":"0dba9a225b41d7f70cdd152679e2d93c1baf9e3897cbe8365a494c212b3d7a91","state":"completed","submissions":[{"artifacts":[],"attempt":1,"bundleHash":null,"device":"ad944e1953b3faa2","findings":[{"citation":"resolved","description":"Now: The API unit tests and browser scenario runner load artifacts/api-observations.json, but that file is absent from the delivered tree. The README also links to this missing evidence for the claimed real-value calibration.\nChange to: Include the actual public API capture at the referenced path, or update both runners to use an included, clearly identified capture. Keep synthetic scenario mutations labelled as test data.\nWhy: The brief requires API calibration against real values and tests covering active, idle, stale, outage, schema and duplicate-event behavior; the delivered checks must be runnable to verify those claims.","line":12,"path":"tests/api.test.ts","reproduction":"Width: not applicable (test runner). Install the package.json dependencies, then run npm test from the repository root. It exits 1 with ENOENT opening artifacts/api-observations.json at tests/api.test.ts:13; 15 game/storage tests pass but tests/api.test.ts fails before any API case executes. scripts/browser-tests.mjs:8-10 reads the same absent file before launching a browser. Expected: the delivered API and browser tests can load their fixture and execute. Replaying the unchanged test sources in an external temporary copy with a newly captured public status/events file executes all 29 tests successfully, confirming that the absent input is the blocker.","severity":"medium","snippet":"const captured = JSON.parse(\n readFileSync(\"artifacts/api-observations.json\", \"utf8\"),\n);","title":"bug: API validation tests depend on an absent capture file"},{"citation":"resolved","description":"Now: Ending a shift removes both the condition meters and Read shift log. The result gives a total score, remaining power and a generic outcome, so the final turn has no inspectable numeric feedback even though its full record is saved.\nChange to: Keep the existing shift-log disclosure visible for any run, below the result as well as during play. Reuse the existing condition-value presentation for the three final conditions in the result; close any vacated space by letting the following workshop move up.\nWhy: A strategy-game result should let the player see how their last allocation affected the burrow and score before starting another shift. This reuses existing feedback rather than requiring another feature.","line":640,"path":"src/App.tsx","reproduction":"Width: 390 CSS px, height: 844. Open a fresh profile, choose Play practice, allocate 1 heat, 1 water and 1 repair on each of the six turns, and end each turn. Before ending turn 6, expand Read shift log: there are 5 history rows and 3 .system-meter elements. After ending turn 6, .shift-log and .system-meter each have 0 elements, although the saved practice history contains 6 entries. The result shows 1,801 points and 3 remaining power but no final condition values or access to the sixth-turn allocation/outcome. Expected: the existing completed-turn evidence remains inspectable on the result screen.","severity":"medium","snippet":" {run && run.status === \"playing\" && (","title":"taste: the result screen hides the completed shift log and final conditions"},{"citation":"resolved","description":"Now: The five field-guide section links are rendered as an unlabeled aside inside main, so they are exposed as a complementary landmark rather than named section navigation.\nChange to: Give this existing element role=\"navigation\" and aria-label=\"Field guide sections\", preserving its current layout and links.\nWhy: Assistive-technology users should be able to distinguish the field-guide contents from the site navigation and jump directly to it.","line":1173,"path":"src/App.tsx","reproduction":"Width: 390 CSS px, height: 844. Open How to play and inspect its accessibility tree or run @axe-core/playwright on that route. The five links The goal, Your turn, Wheel power, Digging deeper and Scoring & saves are inside an unnamed complementary landmark nested in main. Axe reports landmark-complementary-is-top-level (moderate impact) for this aside. Expected: the links are exposed as a navigation landmark named Field guide sections.","severity":"low","snippet":"