data2dsl

Ticket 081: Preserve bounded readiness scope

• ID: ticket-081
• Owner: founder:tom-sapletta-com
• Status: DONE
• Workflow state: DONE
• Created: 2026-08-30

Goal and scope

Preserve the bounded readiness_scope scalar emitted by runtime registries so consumers can distinguish local executable presence from credential, account, or provider readiness without widening discovery authority.

Acceptance criteria

• AC-01: SESSION_EXECUTION_AUTHORIZATION is inherited from the Founder’s request to repair Data2DSL regressions autonomously.
• AC-02: readiness_scope is part of the closed operational attribute vocabulary and remains subject to existing scalar and secret bounds.
• AC-03: Regression tests preserve local_executable and reject a secret-shaped value in the same field.
• AC-04: Full tests, Ruff, governance, protected review, merge, and live Supervisor graph readback pass.

Validation evidence

• Complete suite: 145 passed; the pre-existing jsonschema deprecation warning is unchanged.
• Ruff passes for the discovery core and regression fixture.
• Managed governance reports zero errors and warnings.
• Protected Validator merged exact head 9d217b98120875d7391f94d74a6d42171f2a84d2 through PR #76 as fd623d092d90af54be544dcc4cccf3c87e139d21. The installed runtime readback preserves local_executable on all 16 Hub tool nodes while Supervisor remains healthy with zero warnings/redactions.

Source

• github://autogrammar/data2dsl/issues/75

Participants

• Human participant: Founder authorization is recorded from the active session; no user-* file was created by the agent.
• Agent participant: ai-codex.md