pokt-network

Curate FilePlugin fixtures for a poktroll version from the Hetzner archeology bucket — download, scan, select per spec §8.1, generate expected.json, enroll in the golden walker. Use when a new version's tarball lands in the bucket (v0.1.30 / v0.1.31 / v0.1.33…

Onboard a new poktroll chain version — vendor protos, codegen, scaffold decoder, register in router, add CI matrix. Use when poktroll publishes a new release that introduces protobuf changes.

Scaffold a new continuous aggregate (rewards_hourly, claims_daily, etc.) following PocketScribe's registry-driven pattern with bucket sealing. Generates migration, registry entry, sealing test, and late-arrival test.

Scaffold a new consumer module (supplier, application, gateway, etc.) following PocketScribe patterns — generates the consumer Go code, SQL migration, tests, and CLI registration. Enforces TDD by generating tests first.

Onboard a poktroll chain version. Vendors protos at the given tag, extracts a structural snapshot of every poktroll-owned message, and computes the diff against the previous vendored version. Produces docs/research/.shapes/<vX_Y_Z>.json (full snapshot) and…

Generate a goose SQL migration for a specific poktroll version from its shape snapshot. Reads docs/research/.shapes/<vX_Y_Z>.json (produced by /generate-decoder), compares against the immediately-previous snapshot, and emits…

Audit recent changes (staged, uncommitted, or last N commits) for violations of PocketScribe's hard invariants. Fast guardrail before commit.

Full pre-commit gauntlet — runs gen-check, lint, unit tests, invariant audit. The skill version of `make ci` plus invariant checks.

Use when starting any unit of work — a finding, a bug, a feature, a queue item — to run it end to end under this repository's process, from sizing it against the tree to closing it in the queue.

Use when about to claim work is done, before committing or pushing, or when asked whether something broke — runs this repository's quality gates at the right level and reports what was verified and what was not.

Use after writing a test, after a test passes on the first try, or before trusting an existing test as evidence — proves the test actually fails when the defect it claims to catch is present, by injecting that defect and reverting it.

Use when wrapping up a work session, writing a hand-over, or about to say the work is left ready — enumerates what the session opened, proves each item reached the queue, and carries the work through to asking for push and PR.

Use when a quality gate, test or CI job goes red — classifies the failure as caused by your change, pre-existing, or environmental, and says what to do about each. Use before re-running anything.

Judge whether a feature is actually PROVEN before it is declared complete — whether the tests and the live matrix exercise it against the acceptance criteria written before the work. Use when a feature's work is finished and green, before any adversarial…

Use at the opening of a session, before any work — verifies the machine against what the hand-over claims, reports every divergence, and does not let work begin on an unread queue or an unstated plan.

Use when a whole AREA is suspected of passing for the wrong reason — a suite that never goes red, a flake with no red to start from, a mutation that stayed green, code written fast. Audits by INJECTING a dependency's worst behaviour and reading what fails,…