Production: selectively promote Writing scale epic #661 - #676
Merged
Conversation
Deploying suyogjoshi-dev with
|
| Latest commit: |
87ba9be
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7a167033.suyogjoshi-dev.pages.dev |
| Branch Preview URL: | https://release-661-writing-producti.suyogjoshi-dev.pages.dev |
suyog19
marked this pull request as ready for review
August 28, 2026 15:57
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.
Selective production scope
This release intentionally promotes only:
It is based directly on production commit
3e1fe8e005989a081ae73f0f1d67d5d24725a6a7. No intervening dev merge commits or unrelated issue changes are included.Validation
The two generated bootstrap version lines retain the upstream Markdown hard-break whitespace already used by the generator; generated files were not hand-edited.
Canonical policy correction
The restriction reported on the previous candidate was traced to a latent mismatch in
software-engineering-process: the intended human-controlled production boundary had been mapped to an unconditional two-human GitHub Environment gate.The correction was recorded in software-engineering-process#5, implemented and manually merged through software-engineering-process#6, and released as process version
1.0.1at immutable revision:3f353cf48660f20883304cad07391966c3807e45This PR now pins that exact version and revision. The resolved policy requires:
Production-control status
Product Owner approval was explicitly provided in the delivery thread. Objective validation passes under the corrected canonical policy.
Because the policy upgrade creates a new exact PR head, fresh-context independent review must be rerun against the updated candidate before merge. This implementation context does not issue that verdict.
Final production merge remains manual and human-controlled. Automation and this agent must not merge or enable auto-merge.
Rollback
Revert the eventual production merge commit. There are no database migrations, host/domain changes, runtime state migrations, or dependency changes.
Relates to #661 and #674.