Skip to content

GEN-2824 add bounded bearer forwarding - #375

Draft
asselstine wants to merge 104 commits into
mainfrom
GEN-2824-proxy-forwarding
Draft

asselstine wants to merge 104 commits into
mainfrom
GEN-2824-proxy-forwarding

Conversation

@asselstine

@asselstine asselstine commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Current checkpoint — 02492a025c63f1219ea116bae2585e75191674c0

  • Preserved the existing PR branch and checkpoint commits. Reconciled origin/main at d13fb4a8d8db981a031578ca085c1515abf9adbd in cdf1d029ae4a054170e3565d4c4626c26bea3c14.
  • Added a boot-bound, authenticated proxy runtime status heartbeat. Boot registration defaults locked; new boots clear prior unlocked state. Scheduler now reads fresh status and blocks credential-dependent launches unless the proxy is registered, enabled, and unlocked. Stale heartbeats fail closed.
  • The first push was rejected because the remote branch moved to rewritten checkpoint commit IDs. Merged that remote history without force-pushing; merge commit 02492a025c63f1219ea116bae2585e75191674c0 has the same tree as validated commit 28dd751ca62df794faa07866586019b64626af36.

Validation on tree 28dd751ca62df794faa07866586019b64626af36 (identical to current head tree)

  • Node 24.12.0 / npm 11.19.0; clean npm ci; isolated local PostgreSQL; Chromium installed locally.
  • npm test passed: backend 642 passed / 5 skipped; compiled app/API/PostgreSQL integration 2 passed; Chromium functional 7 passed; app unit 99 passed / 1 skipped; proxy harness 4 passed; credential proxy 63 passed; generated contracts, package/API boundaries, docs, runtime checks and dry-run deploy checks passed.
  • git diff --check passed. Synthetic credentials/local fixtures only; no live Fly/ChatGPT checks or production deployment.

Remaining acceptance work

  • Complete the persisted proxy lifecycle and state-to-block-to-manual-retry PostgreSQL/API integration coverage.
  • Implement Fly app/Machine execution for code and Codex jobs with local API/guest fixtures; collect results, logs and artifacts before cleanup; cover failure, cancellation, timeout and ambiguous-create recovery.
  • Implement shared factorize-job startup/supervision and custom image launch prerequisite checks.
  • Complete integration management/API boundaries, remaining lifecycle/revocation, packaging/docs and end-to-end acceptance.

This remains an incomplete checkpoint. Keep GEN-2824 In Progress and PR #375 draft. GitHub Build Manager owns asynchronous PR checks and merge-queue monitoring; this run did not poll them.

@linear

linear Bot commented Nov 11, 2026

Copy link
Copy Markdown

GEN-2824

@asselstine
asselstine force-pushed the GEN-2824-proxy-forwarding branch from 8a4ca17 to f1ff6ad Compare November 11, 2026 20:33
exe.dev user and others added 26 commits November 12, 2026 06:06
@asselstine
asselstine force-pushed the GEN-2824-proxy-forwarding branch from eda72e9 to a5c6d8d Compare November 12, 2026 06:19
exe.dev user added 3 commits November 12, 2026 06:19
…GEN-2824-proxy-forwarding

# Conflicts:
#	packages/api/src/postgres/proxy-control-repository.ts
#	packages/api/src/postgres/run-scheduler.ts
#	packages/api/src/proxy-control.ts
#	packages/api/test/proxy-control.test.ts
#	packages/credential-proxy/src/control-client.mjs
#	packages/credential-proxy/src/main.mjs
#	packages/credential-proxy/test/control-client.test.mjs

This branch has not been deployed

No deployments
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