Skip to content

docs: Phase Q plan — adopt canonical sc-publish workflow - #525

Closed
randlee wants to merge 3 commits into
developfrom
plan/sc-publish-migration
Closed

docs: Phase Q plan — adopt canonical sc-publish workflow#525
randlee wants to merge 3 commits into
developfrom
plan/sc-publish-migration

Conversation

@randlee

@randlee randlee commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds docs/phase-Q/phase-Q-plan.md: phase goal (replace sc-compose's independently maintained publishing implementation with the canonical sc-publish package), non-goals, and the Q.1/Q.2 sprint sequence and shared contracts.
  • Adds docs/phase-Q/sprint-q-1-sc-publish-package-parity.md and sprint-q-2-sc-compose-publish-cutover.md.
  • Includes the uniffi-bindgen-go sibling-plugin-independence addendum to Q.1, formally closing the traceability gap quality-mgr flagged during PR Release: sc-compose observability integration phase (S2+S3+S4) #29's review (QM-I1).

Note

This docs-only PR was not run through quality-mgr's plan_gate review before sprint work started on Q.1/Q.2 — that step was skipped this phase. Filing it now for record; Q.1 (sc-publish PR #29, merged) and Q.2 (sc-compose PR #524, in QA) implementation work has already proceeded against these docs.

Test plan

  • Docs only, no code changes.
  • git diff --check

🤖 Generated with Claude Code

randlee and others added 3 commits August 19, 2026 18:50
Closes the traceability gap req-qa flagged on PR #29 (uniffi-bindgen-go
moved to a sibling plugin path, not the nested one the sprint doc
originally enumerated). Code was already reviewed clean; this just
documents the relocation as in-scope for future audits.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…gration

# Conflicts:
#	docs/phase-Q/phase-Q-plan.md
#	docs/phase-Q/sprint-q-1-sc-publish-package-parity.md
#	docs/phase-Q/sprint-q-2-sc-compose-publish-cutover.md
#	docs/project-plan.md
@randlee

randlee commented Aug 20, 2026

Copy link
Copy Markdown
Owner Author

Closing: this branch was updated from develop and merge conflicts resolved by team-lead (per user instruction, not delegated to comp). Post-resolution, git diff origin/develop HEAD is empty — the branch is byte-for-byte identical to develop and has no unique remaining content (all of it landed via other merged PRs, including Q.3). No merge needed.

@randlee randlee closed this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant