Repository navigation
Integrate Mission Control and clean up fork CI - #2
Merged
Merged
Conversation
…ssion-control-integration
This was referenced Nov 3, 2026
SaiFlyBy
marked this pull request as ready for review
November 3, 2026 20:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Post-merge update: Owner-only Actions policy 10761 is active. GitHub currently reports that workflows on this fork are paused due to Actions usage. The contributor-approval status described below was the earlier state.
Worktrunk worktrees need a direct way to carry Mission Control's workspace custody, independent verification, and evidence into a scope-at-a-time PR workflow. This adds the v16 template and a bridge that prepares and registers a worktree at the compiled base, reports and settles a scope, and publishes an independently accepted head as a draft PR.
The bridge preserves resource-claim admission and workspace reconciliation. When main advances after acceptance, its handoff creates a successor for reassessment and allows still-valid evidence to be reused; it does not require a local aggregate branch or automatically squash, rebase, merge, or delete worktrees. Publication binds the verified origin destination, retains origin hook and transport semantics, and creates a new branch only when the remote ref is absent. The bounded scope report adapts P-stack's decision-projection idea; source versions, licenses, and the decision not to activate unavailable forge-admission machinery are recorded in
INTEGRATION_PROVENANCE.md.The fork CI no longer uploads test results or coverage to Codecov, runs the inherited Tend workflows, or publishes benchmark results to the upstream bot's gist. GitHub Actions artifacts, source tests, and bridge tests remain. Upstream-owned SignPath and package-publishing jobs were removed; version-tag releases still create GitHub releases and can use Sigstore through packslip. Windows release binaries are unsigned. The standalone release archives do not include Mission Control's Python/template files, so the bridge currently needs a matching source checkout.
The checked-in PR jobs admit same-repository heads and skip unchanged external-head workflows; independently controlled GitHub approval settings are required to enforce this against an external PR that edits its own workflow. The fork's setting currently requires approval only for first-time contributors, so the requested all-external-contributor boundary is not yet enforced. Skipped jobs are not test evidence. The current repository-scoped GitHub Apps list contains neither pre-commit.ci nor Codecov; no app settings were changed.
Validation and limits:
ac5805026f5f943c8658073be4c58c8f8a1773dd, eight CI policy tests, 64 own/external/deleted-fork/push/dispatch expression cases using GitHub's expression library, actionlint, 19 template-coherence tests, offline Cargo metadata, and the pinned cargo-dist release plan passed. Tend 0.3.23's normal generator emitted no workflows. The planner generated fork-owned release URLs and no unconfigured Homebrew installer.macos-26with the same test command and setup. Other longer nightly jobs are still running. The inheritedpull_request_targetTend review fails because the base workflow requires an unavailable bot token; the candidate removes it after merge.4ed759cefa331e130e5055b670a5796988877388, 25 bridge tests and 19 template-coherence tests passed locally; the cleanup does not change bridge or Rust source, but does change Cargo repository metadata and CI definitions.wt cbc4b8afbbinary. This is not a complete retained-template qualification for the new head. Bridge publication tests use local Git remotes and a simulated forge; they do not exercise a live HTTP proxy or GitHub push. Independent acceptance and the repository-level external-contributor approval setting remain outstanding.