-
Notifications
You must be signed in to change notification settings - Fork 0
Logbook July 2026
- Merged ux-judge: automated UX/UI feedback loop scored vs CQuisitor rubric #132
- Merged ux-judge P1 burn-down — demote Books, dim empty fields #133
Week of Jul 6 — The teal MD3 redesign got its final correctness pass and shipped. Monday's hardening made the examples reflect their claims — bundled SHACL shapes synced behind a drift guard, banner counts and empty/zero field display corrected, and the fired shape surfaced; the full input, decoded, and validation restyle with its responsive no-overflow lock then merged on Friday. Sunday opened a credential-resolution slice that resolves opaque credentials by a generic hex suffix, carried into the next week.
- Opened feat: resolve credentials by generic hex suffix #148 — resolve opaque credentials by matching a generic hex suffix, with a spec slice and a gate smoke
Week of Jul 13 — A consolidation and honesty pass on the inspector. Credential resolution by hex suffix merged Monday; Tuesday made the ledger and SHACL verdicts truthful and separate, restored the decoded-result hierarchy the loaded-screen redesign had broken, exposed the protocol registry as a flake output, and added a local CI entry point. Wednesday turned the inspector offline-first and provider-explicit — Koios browser access disabled and reported honestly, local decode offline by default — demonstrated transaction-scoped Structure resolution, and slimmed the inspector down onto the shared engine repo. The week closed Thursday by recording the structural CBOR span feasibility stop: the pinned cborg fork exposes direct-offset primitives but no bounded probe proved the span assertions, so exact original-byte spans stay unproved, not disproved, with no production change.
- Merged feat: resolve credentials by generic hex suffix #148 — resolve opaque credentials by a generic hex suffix so entities surface with readable identities
- Merged fix(inspector): render truthful ledger validation verdicts #154 — separate ledger and SHACL verdicts and normalize the ledger verdict contract so the UI reports what actually validated
- Merged Restore decoded-result hierarchy after the loaded-screen redesign #153 — restore the decoded-result hierarchy the loaded-screen redesign had flattened
- Merged feat: expose protocol registry as a flake output #152 — expose the protocol registry as a flake output for downstream consumers
- Merged chore: add local CI entry point #151 — add a local CI entry point mirroring the gate
- Merged Make the Inspector offline-first and provider-explicit #155 — local decode offline by default, explicit provider dispatch, and Koios browser access disabled with its CORS limitation reported honestly
- Merged feat: demonstrate transaction-scoped Structure resolution #156 — demonstrate credential resolution scoped to a transaction in the Structure view
- Merged refactor: slim inspector to engine repo #158 — slim the inspector down onto the shared engine surfaces, redirecting the pages build to the csk workbench
- Merged Document final structural CBOR span feasibility stop #157 — record the final feasibility stop for exact structural CBOR source spans (closes #140); the pinned cborg fork exposes direct-offset primitives but no bounded probe executed the span assertions, so exact original-byte spans remain unproved, not disproved, and no production Haskell, schema, or gate change lands
Week of Jul 20th — The wrapper enrichments deepened and started converging. Monday exposed lossless typed auxiliary metadata on
tx.intent, preserving nested values with exact integer strings and map order. Wednesday published the Amaru deployment as a generic Turtle book and decoded registered output datums and script redeemers by embedding the tracked protocol registry into the WASI build. Friday opened the cross-target refactor that moves those enrichments into the reusableConway.Inspectorlibrary so WASI, native, and the Extism plugin share one boundary.
- Merged feat: decode auxiliary transaction metadata #161 — expose lossless typed auxiliary metadata at
result.intent.auxiliary_data.metadata, preserving nested int, bytes, text, list, and map values with exact integer strings, lowercase byte hex, and map ordering, while retaining themetadata_claimscompatibility view (closes #160)
- Merged docs: publish Amaru deployment Turtle book #163 — publish
journal-2026.ttlbeside the pinned Amaru journal so transaction-book consumers resolve Amaru owners, treasury addresses, scripts, and deployment outrefs through generic Turtle instead of the deployment-journal JSON schema
- Merged feat: decode registered Plutus data in tx.intent #164 — embed the tracked protocol registry into the WASI build and decode registered output datums and script redeemers in
tx.intent, preserving raw/generic data for unknown scripts and covering the treasury and SundaeSwap V3 fixture clusters (closes #35)
- Opened refactor: share tx.intent wrapper across targets #166 — move the
tx.intentenrichments into the reusable localConway.Inspectorlibrary so WASI, native, and the Extism plugin expose the same typed auxiliary metadata and registered datum/redeemer annotations, proven by byte-for-byte response comparison (closes #165)