Skip to content

Run approved external recipes with verified descendant custody - #48

Closed
MrScripty wants to merge 2 commits into
feature/scoped-local-actors-20261013from
feature/approved-external-recipes-20261013
Closed

MrScripty wants to merge 2 commits into
feature/scoped-local-actors-20261013from
feature/approved-external-recipes-20261013

Conversation

@MrScripty

@MrScripty MrScripty commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Integration disposition — 2026-10-14

Current reconciliation (2026-10-14): qualified generic content from this original stack is superseded and integrated in merged PR56 on main, without unqualified PR43 ancestry. This original draft/branch remains retained as source/evidence and for any producer-v2-specific dependent guards. It is no longer a pending generic-feature merge. Do not merge the deferred legacy stack wholesale; its original actual-data acceptance remains open.

Original source and qualification record follows:

Scientific project recipes previously could be inspected but not executed through Tuldok. This milestone adds editable input → execute → output graphs, exact material preflight, one-use owner approvals for scoped agents, and verified external results through the existing Runs queue. The pinned helper owns the READY/GO barrier and descendant drainage; uncertain cessation remains visible and fences further external execution.

Schema 8 retains schemas 1–7 and adds approval/consumption evidence. The UI supports typed parameters, owner and approved-agent submission, cancellation, artifact downloads and restart. This is explicitly trusted local code with same-user filesystem/network authority, not a sandbox. Existing CPU/integrity execution remains separately qualified and owner-only.

Validation: 50 approval/storage tests, 28 host/retained graph tests, 11 real helper lifecycle tests, and 15 composed Runs/HTTP tests pass. Real desktop/narrow browser workflows cover exact review, stale bytes, owner/agent execution, cancellation and restart. Native Rheon ready/stop passes behind the helper; no simulation/model acceptance is claimed. The full stable-source suite at c8ba1ad passes749 tests (two optional-reader skips separately covered20 tests); all176 Python files remained unchanged. Existing31 JS checks plus the new external controller pass. Final independent backend/UI review reports no remaining blocker. A narrow interpreter-version path correction additionally passes6 host tests,4 real HTTP tests and the complete browser workflow. Exact published head 7d59060 passed hosted UI 38440828965 and lifecycle 38440828870, all 132 steps.

Evidence: admission, contract, verification, native probe. Stacked on PR47; draft only, no merge or deployment.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Owner Author

Closing this original stacked proposal as selectively incorporated or superseded by merged #56 (generic scientific core) and #57 (generic scoped MCP).

Approved external execution, READY/GO descendant custody and scope/grant ownership incorporated through PR56; current main substantially extends exact composition grants and custody.

Independent cleanup review checked this exact head 7d590605006f48f6c3f710b91a75ad4455d0a9d7 against main ab2ca5ba225ae6f8fa91ce7dd743ba1e48ea72a0 and the admitted selective-integration lineage. Deferred controls-v2 and complete original P6/G7 scope remain preserved in open #43 and #53; this closure does not claim those gates passed.

The original branch is retained. Its head is not ancestral to main, so this cleanup neither deletes its history nor merges its excluded ancestry.

@MrScripty MrScripty closed this Oct 16, 2026
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