docs(agents): merge release-* playbooks into release.md (init 0009 PR 2.3)#1718
Closed
Skords-01 wants to merge 5 commits into
Closed
docs(agents): merge release-* playbooks into release.md (init 0009 PR 2.3)#1718Skords-01 wants to merge 5 commits into
Skords-01 wants to merge 5 commits into
Conversation
… 2.3)
Consolidate three narrowly-scoped release playbooks into a single
docs/playbooks/release.md with a mermaid decision tree and three
sections:
- Web + API
- Mobile shell (Capacitor)
- Expo
Old files (release-web-and-api, release-mobile-shell, release-expo-mobile)
become Status: Deprecated stubs that link to the new sections, so
existing bookmarks, audit logs, and PR references keep resolving.
Update references in:
- specialists mapping, service catalog, release policy
- playbook catalog and INDEX (regenerated)
- run-weekly-operator-digest, retire-feature-flag
- sergeant-review-and-merge / sergeant-web-ui / sergeant-server-api /
sergeant-mobile-expo SKILL.md (skills-lock regenerated)
Note: schema status enum is {Active, Scaffolded, Deprecated, Archived}
(AGENTS.md Hard Rule #10), so old files use Status: Deprecated with an
explicit "Superseded by:" line pointing to the merged playbook.
Co-Authored-By: Ка А <dmytro.s.stakhov@gmail.com>
Follow-up to the trigger-length fix on docs/playbooks/release.md (\u2264 240 chars per playbook-schema): regenerate INDEX.md so the trigger column matches the playbook source. Also restores the auto-generator freshness marker (`by @devin-ai`). Co-Authored-By: Ка А <dmytro.s.stakhov@gmail.com>
Co-Authored-By: Ка А <dmytro.s.stakhov@gmail.com>
Pre-existing violation on `main`: Trigger was 275 chars > 240. The schema gate is enforced in the same CI job as the playbook trigger index check, so it has to pass for this PR's CI to go green. Mirrors the fix already proposed in PR #1693; included here so PR 2.3 does not block on the merge order. Co-Authored-By: Ка А <dmytro.s.stakhov@gmail.com>
Co-Authored-By: Ка А <dmytro.s.stakhov@gmail.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
9 tasks
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (17)
📝 WalkthroughWalkthroughThis PR consolidates release playbooks across four production surfaces into a single canonical playbook. A new ChangesRelease Playbook Consolidation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 6/10 reviews remaining, refill in 22 minutes and 16 seconds. Comment |
⏱️ CI Pipeline Duration ReportBased on the last 50 successful runs on the default branch. Overall Pipeline
Trend (last 20 runs): Per-Job Breakdown
|
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.
Summary
Phase 2 PR 2.3 of initiative 0009. Replaces #1705 (closed because the GitHub PR head ref got stuck at
d739add2and would not resync after pushing the deploy-config-change.md fix; closing did not allow reopen). Same branch, same content, plus the schema-fix commit that PR 1705 was missing.Merges the three narrowly-scoped release playbooks into one consolidated
docs/playbooks/release.mdwith a mermaid decision tree and three sections (Web + API, Mobile shell (Capacitor), Expo). Old files becomeStatus: Deprecatedstubs that point at the matching section.docs/playbooks/release.md— H1, freshness, Status, ≤240-char Trigger, Owner surface (sergeant-deploy-and-observability), decision tree, three numbered sections, Verification with 6 checkboxes, when-not-to-use, related.release-web-and-api.md,release-mobile-shell.md,release-expo-mobile.mdkeep a stable URL for incident logs / past PRs / git blame and link torelease.md#…anchors.docs/agents/specialists-mapping.md,docs/architecture/service-catalog.md,docs/governance/release-policy.md,docs/playbooks/playbook-catalog.md,docs/playbooks/INDEX.md(regenerated),docs/playbooks/run-weekly-operator-digest.md,docs/playbooks/retire-feature-flag.md, four SKILL.md files (sergeant-review-and-merge,sergeant-web-ui,sergeant-server-api,sergeant-mobile-expo) and.agents/skills-lock.json.docs/playbooks/deploy-config-change.md(was 275 chars > 240 schema cap; pre-existing onmain). Mirrors the same fix proposed in docs(docs): mark initiative 0011 phase 1 as complete (4/4 merged) #1693; included here per user request to make CI green for the consolidation PR — no other change to that file.Status semantics note: the playbook schema enum is
{Active, Scaffolded, Deprecated, Archived}(AGENTS.md Hard Rule #10). The initiative spec used the word "Superseded"; we keep theStatus:line schema-valid and add an explicit> **Superseded by:** [release.md § …](…)line right under it, which matches the existing "Deprecated — describes a behaviour we are replacing; reference the replacement" rule.Validation
pnpm docs:check-playbook-schema→ OK (44 playbooks).pnpm docs:check-playbook-index→ OK after regeneratingINDEX.mdand shortening the new release.md Trigger to 236/240 chars.pnpm lint:skills→ OK (12 skills).pnpm docs:check-links --no-external→ only pre-existing broken internal links (5, all unrelated to this PR).pnpm format→ OK.Hard Rule #5 (Conventional Commits)
docs(agents)for playbook/skill consolidation).Hard Rule #15 (freshness headers)
Last validated: YYYY-MM-DD by @owner. Next review: YYYY-MM-DD.header.pnpm docs:check-playbook-schema) passes for all 44 playbooks (Trigger ≤240 chars, Status enum, Owner+Governing skill, Verification ≥1 checkbox).docs/playbooks/). Ukrainian translation of operator-facing playbooks is its own follow-up tracked in the initiative.Summary by cubic
Consolidates the three release playbooks into a single canonical
docs/playbooks/release.mdwith a decision tree and sections for Web + API, Capacitor shell, and Expo. Deprecates the old playbooks, updates references across docs, and fixes a trigger-length schema error to keep CI green.docs/playbooks/release.md(decision tree, three sections, verification checklist).release-web-and-api.md,release-mobile-shell.md, andrelease-expo-mobile.mdas stubs that link to the new anchors.sergeant-*SKILL docs; refreshedskills-lock.json.deploy-config-change.mdto meet the ≤240-char schema cap; regenerated the playbook index.Written for commit 2311c3c. Summary will update on new commits.
Summary by CodeRabbit