Skip to content

feat(ground): add regional execution evidence readback - #4351

Closed
d-sorgcodexagent[bot] wants to merge 3 commits into
feat/4271-regional-execution-bindingfrom
feat/4271-regional-execution-ui
Closed

feat(ground): add regional execution evidence readback#4351
d-sorgcodexagent[bot] wants to merge 3 commits into
feat/4271-regional-execution-bindingfrom
feat/4271-regional-execution-ui

Conversation

@d-sorgcodexagent

Copy link
Copy Markdown
Contributor

What changed

  • add a bounded, strict Python adapter for canonical ground-regional-execution-result/v1 evidence
  • add matched PyQt6 and React evidence readback panels bound to the exact visible regional material plan
  • invalidate stale evidence after plan edits and preserve previously accepted evidence after failed imports
  • report truthful execution status, termination, model identity, skid/roll/total distance, surface transitions, provenance, and qualification limitations
  • update the campaign manifest, SPEC, and canonical handoffs in the implementation commit

Why

Regional surface plans and the Python execution contract existed, but users could not inspect a frozen execution result on either application surface. This slice closes that evidence-readback gap without duplicating or approximating physics in the browser.

User and developer impact

Users can import a Python-produced result and verify that it belongs to the exact plan currently shown. React remains an import-only consumer and explicitly performs no physics. Native file reads are byte-bounded and strict UTF-8; both surfaces fail closed on mismatched plans or malformed envelopes.

Validation

  • 207 Python ground, plan, PyQt, and layout tests passed in the implementation review
  • 111 React files / 690 tests passed in the implementation review
  • independent root verification: 4 Python and 4 React focused tests passed
  • MyPy, Ruff/format, TypeScript, ESLint, production build, manifest, documentation, structural-budget, and diff checks passed

Addresses #4271
Part of #4267

@d-sorgcodexagent

Copy link
Copy Markdown
Contributor Author

Current-head CI repair: 351a3051e9093c6b80cabf0f1db04aeeb15abfac

The previous protected quality-gate failure was a real static-boundary issue, not a runtime failure: with CI's --follow-imports=skip, the imported atomic writer is typed as Any, so returning it directly violated no-any-return. The current head assigns that result to an explicitly typed bool local. This passes both exact MyPy 1.13 skipped-import configurations (adapter alone and adapter + helper roots) without restoring the root-dependent redundant cast.

Evidence on the exact head:

  • protected quality-gate: success
  • independent focused verification: 16 regional plan I/O and evidence-readback tests passed
  • candidate verification: 24 focused tests plus Ruff/format, docs, manifest, and diff gates passed

Normal child-first propagation through #4352, #4353, and #4354 remains required; this comment does not claim those descendants or the parent epic released.

@dieterolson

Copy link
Copy Markdown
Collaborator

Consolidated into #4409. Closing to reduce CI/CD runner load.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant