Repository navigation
docs: deploy procedure follows the supervisor-start cutover order; tooling tied to steps (#78) - #79
Merged
Conversation
…fers (#78) Follow-up to #74/#77. Fixes the parts of the deploy procedure that do not depend on the open cutover-order decision recorded in #78: - name the kept iso-test/fold-test checks in step 1 and point it at the build recipe in step 3 - say where live-entry.ts and build.mjs live and how the build is run - resolve step 5's contradiction about which launcher defaults change - separate the in-cutover rollback from Rollback-MasterDeploy.ps1 and define step 10 on the rollback path - cite the receipt's masterBackupRoot for the tooling, and describe Rollback-TunedLiveProxy.ps1 as the deeper pre-tuning rollback - record 4b6687b-live in the superseded history - remove the step 9 en/zh drift Steps 6-9 are not rewritten. The page now states what Deploy-Master.ps1 does at cutover and that it differs from those steps. Assisted-by: Cindy (https://cindy.app)
📦 Built Package ArtifactBranch: Download artifact
tar xzf billion-context-pr79.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner decision of 2026-11-16 on issue #78 section A: - The sanctioned cutover order is the one the kept Deploy-Master.ps1 implements: hold supervision, edit the launcher, stop the old proxy when idle, lift the hold and let the supervisor start the new release, check with supervision running. Steps 4 and 6-10 are rewritten to that order in English and Chinese. - A failed rollback ends with the hold back in place and a report to the owner. The page says the kept scripts re-enable supervision regardless, so the hold has to be applied by hand after them. - Step 5 no longer repeats the current release identity; it names the candidate and receipt fields that carry it. Docs only. Nothing was run against the live proxy. Assisted-by: Cindy (https://cindy.app)
- Step 9: supervisor-status.json has no version or commit field; verify the monitored child and healthMatch there and the version and commit from the health endpoint. The restored proxy may be adopted, not started. - Step 6: the kept script waits 90 s for health only, then checks the process counts once. - Step 8: a candidate proxy exists only if the cutover got that far. - Tooling paragraph: the script's receipt rewrite is the one step 7 describes, not step 10's finalization. Assisted-by: Cindy (https://cindy.app)
anuzzolilli-oss
marked this pull request as ready for review
November 17, 2026 23:54
|
(ai: openai/gpt-6-astra) Code Review SummaryStatus: No Issues Found | Recommendation: Merge Light documentation review at Files Reviewed (2 files)
Both Chinese counterparts are present; translation contents were excluded under Reviewed by gpt-6-astra · Input: 42 · Output: 4.2K · Cached: 877.2K Review guidance: REVIEW.md from base branch |
Closed
26 tasks
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.
Scope
Closes #78. Follow-up to #74 / #77. Docs only: four files, no source, test, config or env change.
docs/cindy-project.md+docs/cindy-project.zh-CN.md(first commit only)reference/cindy-project.md+reference/cindy-project.zh-CN.mdThree commits:
4f94dad27covers section B of #78,22d4580abcovers section A, and46be1dfefcorrects four statements in the section A text after an independent read-only check against the scripts (status-file fields in step 9, the 90-second wait in step 6, the candidate proxy in step 8, one step reference in the tooling paragraph).Owner decisions (2026-11-16)
Section A of #78 was an open owner decision. The owner answered three questions in chat on 2026-11-16:
Deploy-Master.ps1implements (supervisor starts the new release)Reading confirmed by the owner (2026-11-17). Under the script order the supervisor also starts the restored release, which needs the hold lifted. "Stay inhibited" therefore means: lift the hold to start the previous release, check it, and if it fails put the hold back (inhibit set, task disabled, supervisor stopped), leave any proxy process as it is, attempt nothing further and report.
What changed for section A (
22d4580ab,46be1dfef)build-info.jsoncommit, the release directory, the version from the step 1 test); the release being replaced is in the launcher defaults and in named receipt fieldsPollSeconds" are now true at this point because supervision is running. States the success test and the rollback triggerDeploy-Master.ps1to steps 2, 4–5, 6 and 8, and to the receipt rewrite that step 7 describesThe third open item in #78 section A (how a hand-started proxy comes under supervision) no longer applies: nothing is started by hand under this order. The closing paragraph says so.
The kept scripts were not edited. Bringing them in line with the failed-rollback end state would be separate work on the owner's say-so.
What changed for section B (
4f94dad27)iso-test.mjsandfold-test.mjs; the tooling paragraph maps each kept file to its stepmasterBackupRoot(currentlybefore-master-20261114-214204), notes the byte-identical copy in-191918, and says each backup's rollback script targets its own cutoverProxyPath,ExpectedCommit, andExpectedVersionwhen the version changes); notes the kept script edits exactly two lines and does not cover a version changeRollback-MasterDeploy.ps1is described as the undo of one completed cutoverRollback-TunedLiveProxy.ps1misdescribed4b6687bc-liveadded to the superseded history with its cutover backupEvidence basis
Read on 2026-11-16 from the machine, read-only:
Deploy-Master.ps1sections 2–3Deploy-Master.ps1preflight and section 4Deploy-Master.ps1section 4PollSecondsStart-BillionContextProxy.ps1supervision-receipt.jsontaskDeploy-Master.ps1section 5Deploy-Master.ps1catch blockRollback-MasterDeploy.ps1restores the launcher and both receipts, re-enables supervision, checks nothingbefore-master-20261114-214204Deploy-Master.ps1HealthyAstuned-deployment.json(releaseRoot,build),supervision-receipt.json(masterDeploy.proxyRelease)iso-test.mjsbuild.mjs, the test script headersNo credentials or config contents appear; paths are written with
%APPDATA%.Verification
node tools/check-architecture-docs.mjs— all greengit diff --check— clean; CRLF line endings preserved, no bare LFNothing was executed against the live proxy and the live port was not touched. No deployment claim is made.
Noted, not changed
The
docs/snapshot pages and thereference/pages contain a literal user-profile path in a few places. They are already onmasterand outside #78, so they are left for the owner to decide.Assisted-by: Cindy (https://cindy.app)