Repository navigation
Conversation
…ool tenant scoping, snapshot ownership
…'s tenant Adds field 8 so the runtime-manager can scope ExecTool to the VM's owning tenant (ADR 0025). gen/go regenerated with the pinned protoc v6.33.4 + protoc-gen-go v1.36.11 (byte-identical to the tracked stub before the change).
…xecTool/snapshots - spawn.json (version/workload_cmd/env/egress_rules/workload_uid/gid) written at the cert-image root; cmdline kept for compat, manager-owned LANTERN_WORKLOAD_UID appended, caller-set value dropped - RuntimeManager interceptor: VM certs (OU=lantern-vm) refused; shared x-lantern-service-token required (constant-time); prod refuses to start without LANTERN_GRPC_SERVICE_TOKEN, dev warns+allows - ExecTool: tenant mismatch / empty-in-prod -> NotFound (vm_id and run_id paths) - spawn reserves the wire vm_id before boot (concurrent duplicate -> Aborted) - restore_snapshot_id restores through the post-gate backend with ownership check (NotFound cross-tenant/legacy/bogus id); non-restoring backend -> FailedPrecondition; bare firecracker resolves store:// ids - snapshots record tenant_id + real agent_version_id; save streams artifacts (1 MiB buffer, streamed S3 multipart) instead of loading guest memory - ExecTool harness call bounded by deadline + 1 MiB output cap; timeout capped - warm pool cold-starts through the post-isolation-gate backend; keyed by tenant Refs ADR 0025.
… honest snapshot restore (ADR 0025)
Contributor
🔎 Codex cross-audit (agent:audit)Blocking:
These all stem from the new interceptor at services/runtime-manager/src/main.rs plus token enforcement in authz.rs. The fix is to thread the existing I did not run tests; filesystem is read-only in this audit environment. |
Contributor
🛡️ Vuln scan — ❌ vulnerable dependency found |
Contributor
🔷 Gemini cross-audit (agent:audit-gemini)Blocking Issues1. Production Startup / Call Deadlock in
|
Owner
Author
|
Superseded: the history rewrite on this stack accidentally re-signed master's commits (base diverged). Replaced by a range-limited rewrite on ga3/* — see the new GA 1/11 PR. |
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.
Part 5 of 11 of the GA next-gen stack. Replaces #264/#255–#263: same changes, history rewritten to drop a 43 MB build binary committed by mistake, plus part 11 fixing every confirmed Codex cross-audit finding. Base:
ga2/04-harness. Merge in order with a merge commit (not squash).Context, verification and needs-human list: #254 and
docs/roadmap/2026-10-nextgen-sandbox-and-harness.md.Commits in this part: