You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SellYourOutboard generic-web proof exposed a confusing failure mode in POST /v1/drivers/generic-web/preview-refresh.
The GitHub workflow sends a valid OIDC-authenticated request. When provider work runs for about five minutes, the client eventually reports:
401 authentication_required
A valid GitHub OIDC token or browser session is required.
That appears to happen after the useful HTTP window has elapsed and the caller retries with the original short-lived GitHub OIDC token. The visible failure then becomes auth-shaped even though the real issue was provider/health/ingress related.
Need
Launchplane should return or record the real preview refresh result, not a stale-token retry symptom.
Candidate work
Avoid retrying long mutation requests with an already-issued GitHub OIDC token.
Consider making preview refresh an accepted async operation with a record id and poll/read endpoint.
Ensure provider failures are persisted and surfaced in PR feedback/workflow summaries.
Bound synchronous route execution below proxy/token timeout if we keep the current request model.
State: Complete. PR #245 persisted generic-web preview refresh provider results into Launchplane preview/generation records, added optional anchor PR metadata for refresh requests, rejected unparseable preview slugs before provider mutation, and documented the refreshed route contract. Merged to main at ba95add and deployed successfully on 2026-05-04.
Next action: Closed as complete; continue #241 by deciding/fixing #94 and #97 preview proof scope.
Blocked by: Nothing.
Last verified: 2026-05-04 after PR #245 post-merge CI/Security/CodeQL and Deploy Launchplane passed.
Context
The SellYourOutboard generic-web proof exposed a confusing failure mode in
POST /v1/drivers/generic-web/preview-refresh.The GitHub workflow sends a valid OIDC-authenticated request. When provider work runs for about five minutes, the client eventually reports:
That appears to happen after the useful HTTP window has elapsed and the caller retries with the original short-lived GitHub OIDC token. The visible failure then becomes auth-shaped even though the real issue was provider/health/ingress related.
Need
Launchplane should return or record the real preview refresh result, not a stale-token retry symptom.
Candidate work
Related
Current Status
State: Complete. PR #245 persisted generic-web preview refresh provider results into Launchplane preview/generation records, added optional anchor PR metadata for refresh requests, rejected unparseable preview slugs before provider mutation, and documented the refreshed route contract. Merged to main at ba95add and deployed successfully on 2026-05-04.
Next action: Closed as complete; continue #241 by deciding/fixing #94 and #97 preview proof scope.
Blocked by: Nothing.
Last verified: 2026-05-04 after PR #245 post-merge CI/Security/CodeQL and Deploy Launchplane passed.
Relationships
Validation
uv run python -m unittestpassed 668 tests.uv run --extra dev ruff check .passed.uv run --extra dev ruff format --check control_plane/service.py control_plane/workflows/generic_web_preview.py tests/test_service.pypassed.uv run --extra dev mypy control_plane testspassed.pnpm --dir frontend validatepassed.git diff --checkpassed.uv run --extra dev ruff format --check .still reports pre-existing unrelated formatting drift in untouched files.