Prove configuration extraction allocation and lifetime bounds #147

Outcome

Complete the remaining phase, overlap and guest allocation bounds for existing configuration extraction, conversion and merge. Unfunded-context refusal and the config-node charge correction are implemented; this task does not reopen those repairs or claim physical out-of-memory from a conservative accounting failure.

Acceptance Criteria

• Enumerate raw, parsed, conversion, merge, retained and terminal owners and simultaneous populations at the actual SDK/application boundary, including refusal, malformed input and cancellation.
• Prove applicable allocation/ABI/allocator bounds for each selected target before crediting savings. Use independent boundary/allocation controls and preserve the shared additive accounting, workload limits and unknown-state refusal.
• Bind evidence to the current source, artifact, features and configured limits; identify gaps rather than treating native measurements as guest or worst-case proof.
• Reconcile the existing representation's proof with runtime-owned startup/snapshot accounting in Account for runtime-owned configuration and bootstrap limits #130; reuse valid components without double charging or silently dropping initialization/overlap.

Relationships

Parent: #9. Complements #130, which owns the new runtime-configuration representation. Target certification in #72, #73, #74 and #75 must consume this proof where extraction is in the selected closure; no unrelated target is a universal blocker. Coordinate final scope through #33.

Source

Retired ledger: configuration funding boundary and bounded extraction evidence.

Priority, Size, ownership and scheduling require triage; project Status is Backlog.

Resource Proof Responsibilities

Responsible technical role: configuration/resource maintainers.

Next verification action: establish the existing raw/parsed/conversion/merge/retained phase bounds and overlap at the SDK/application boundary, including malformed input, refusal, cancellation and applicable guest allocations. Consume the single runtime-configuration representation delivered by #130; do not reopen its completed implementation or introduce another loader/configuration path.

Source: approved shared resource ownership contract, delivered for review in #162. This records responsibility and the next verification action, not completed proof, target qualification, changed workload limits or permission to close this issue.