Repository navigation
fix(release): deploy all critical InnerOS coordination files using existing trusted runner - #209
Merged
Rafa-Innerchispa merged 2 commits intoOct 20, 2026
Conversation
…d deploy manifest
… isolated fixture
Rafa-Innerchispa
marked this pull request as ready for review
October 20, 2026 03:17
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
1 participant
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.
Root cause confirmed
Existing trusted release workflow
.github/workflows/inneros-local-release.ymlalready exists and targets a private AMD self-hosted runner. Its executor only allowed six files, so releasing it would leave our merged routing/Ruby/coordination code absent from the live platform. Avoid a second host-control mechanism.Scoped change
Extend the exact-file allowlist in
scripts/inneros_local_release_executor.pywith live routing + safety modules (local_execution_plane, coordination_live, human_task_id, ops_task_admission, execution_binding, dev_swarm_dispatch_reconcile, integration_guardian, MCP entrypoint/owner alerts). Add a fixed, explicitraphiia_openai/local_execution_plane.pymirror andplatform/scripts/inneros_coordination_cycle.py. Never copy .env, venv, Mongo, arbitrary paths or symlink targets.Keep existing SHA pin, trusted origin/main ancestor, clean source check, production approval/environment gates, SHA256 per file, snapshots, staged atomic os.replace, all-or-nothing rollback, plan default and no default restart.
Offline tests exercise plan, real temp-directory apply/backup, forced midcopy rollback without production host access. CI included in InnerOS P0 runtime safety gates.
Still required for production
Verify dedicated AMD self-hosted GitHub runner and environment approval. GitHub connector here cannot dispatch workflow_dispatch, so CI merge does not activate runtime. Plan using reviewed main SHA first, then environment-approved apply with independent host canary; Intel failover separately. No external paid model use.