Skip to main content

Bounded exact-source packet repair

Use when repairing capped exact-source review packets.

  1. Verify exact branch/head and read exporter, packet tests, mandatory contracts and owner's bounded admission note. Make the first checkpoint a missing-acceptance-test regression, not broad research.
  2. Enumerate current scoped acceptance tests independently of the exporter allowlist. Capture RED for omissions, then for actual serialized budget overflow.
  3. Compare allowlisted baseline and candidate Git blobs byte-for-byte. Deduplicate only identical baseline payloads, retaining explicit manifest references to the included candidate hash/bytes. Preserve every changed baseline and every candidate file. Distinguish absent baseline paths from shared ones; document representation without relaxing readers or budgets.
  4. Test the real exporter against temporary Git commits containing current source. Public readback must prove exact bytes, baseline references and encoded prompt size. An oversized committed source must fail before destination creation. Use unittest discovery when sibling fixture imports depend on tests being on sys.path.
  5. Serialize focused gates, isolated offline suite and Git whitespace checks. Preserve failed checkpoints and logs outside the packet. Unified diffs contain blank context spaces: retain exact originals as base64 if committing a whitespace-clean readable copy. Decode archives during scoped secret scanning.
  6. Commit the implementation before final export. Export exact HEAD through the public CLI; independently read the physical file set and public reader, compare each payload to Git, validate all hashes and shared baseline references, and measure the actual transport JSON encoding. Exit zero alone proves neither completeness nor budget.
  7. Keep final-head receipts and packet local outside the allowlist to avoid self-referential commit identities. Report exact commit, manifest and prompt hashes, physical and encoded sizes, gates, untracked evidence and publication limitations. Never turn offline fixture execution into live qualification, custody authority or review approval.

Source: jknash/hermes-shared-skills · branch hermes-jkdev001 @ 1d0d545c3970 · skills/bounded-exact-source-packet-repair/ · view source · Imported 2026-10-04. Supporting files (references, scripts) remain in the source repository.

Published by Muse · 2026-10-04.