Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 8340@bnt-lap001 Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
46 lines
2.1 KiB
Markdown
46 lines
2.1 KiB
Markdown
---
|
|
id: APPROVAL-WP-ADHOC-2026-10-16
|
|
type: workplan
|
|
title: "Repair exact consume-confirmation native binding comparison"
|
|
domain: infotech
|
|
repo: approval-engine
|
|
status: finished
|
|
flavor: implementation
|
|
owner: codex
|
|
topic_slug: netkingdom
|
|
created: "2026-10-16"
|
|
updated: "2026-10-16"
|
|
state_hub_workstream_id: "51585baa-f3c3-5203-9f32-3f0a3c94f889"
|
|
---
|
|
|
|
## Refuse Python-equal JSON-distinct consumed act bindings
|
|
|
|
```task
|
|
id: APPROVAL-WP-ADHOC-2026-10-16-T01
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "ff45b583-a021-5a06-bb8d-3ba09674d1f8"
|
|
```
|
|
|
|
Bounded source repair demanded by the CUST-WP-0080 strict execution-seam proof.
|
|
INTENT basis: exact binding and authenticated consumption evidence; no authority
|
|
or native grant is added. Existing canonical native-five-field digest is reused.
|
|
ExecutionConfirmationClient now recomputes the served and expected digests and
|
|
requires the served digest field to correspond, replacing Python dict equality
|
|
which accepted nested True/1, False/0 and integer/float substitutions.
|
|
|
|
Before repair seven regression cases wrongly confirmed (four target type
|
|
substitutions and three absent/wrong/type-invalid served digest fields); valid
|
|
nested types with reordered keys passed. The repair retains this failure history.
|
|
Twelve added regression cases cover exact native JSON correspondence, including
|
|
substitutions with both retained and recomputed served digests, without
|
|
changing the native digest algorithm, request/PDP digest contract or API schema.
|
|
Canonical integration/publication and the Platform mediator's final provider
|
|
client source pin remain with the coordinator; preparation does not claim them.
|
|
|
|
Existing APPROVAL-WP-0004 closure and generated identifiers are untouched.
|
|
APPROVAL-WP-0002-T01/T04/T05 remain existing live native acceptance obligations;
|
|
none is promoted or completed here. No production auth, approval mutation,
|
|
credential, deployment or backend operation was used. This completed low-risk
|
|
local source repair introduces no residual native obligation beyond those
|
|
existing records and the coordinator's integration of this exact artifact.
|