Conversation
Separate configuration and database readiness from business execution. Require exact deployed version, source tag and challenge identity; probe only three metadata RPCs. Preserve existing publishing and rollout controls. Add 63 regressions; no new dependencies or production deployment.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
oneclickpostfactory-agent | 2d00213 | Commit Preview URL Branch Preview URL |
Sep 29 2026, 02:04 PM |
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.
Approved milestone implementation
The owner approved all seven delivery milestones, with no new subscription/paid database branch, no mandatory laptop/WSL execution and no unapproved overage. This PR implements M1's runtime readiness prerequisite; it does not claim all milestones or hosted acceptance are complete.
Base
6e8ac018d4db4ebb726bd69c3a99569adad50a5d; head2d00213a7a2a8aaa37e206cfbb865782b79089cf.Implemented
/readyz, separate configuration and database modes.Preserved boundaries
Existing production deployments, cron configuration, kill switches, tenant cohort, provider gates, billing and schemas are unchanged. No new dependency or lockfile change. No production deployment is requested by this PR. Readiness does not authorise a business effect.
The app-owned cloud harness will independently read active deployment/version metadata, perform bounded effect-free probes, and execute each trial's business ticks once. It must never turn a failed tick into retry-until-green. Previous authenticated 404/500 observations remain failures; a root cause/fix is not claimed from synthetic tests alone.
Validation uses the existing public Worker repository's standard CI only; private schema source must remain private. The app staging orchestration and its capacity/cleanup evidence are a separate paired change.