docs: track upstream contribution strategy with workspace-aware 5-PR revision#13
Merged
stanleykao72 merged 1 commit intomainfrom May 5, 2026
Merged
Conversation
…th workspace-aware revisions Adds the long-tracked umbrella change that maps fork's 26 commits to a 5-PR upstream contribution plan. Originally drafted 2026-04-17 (memory project_openspec_upstream_strategy.md). Updated 2026-05-04 to account for workspace-foundation landing (PR Fission-AI#1045) and TabishB's 21-day silence since the 04-13 PR Fission-AI#891 ack. Key revisions: - T0 icebreaker: marked stalled-not-negative; push T1 to force review - T1 (plugin foundation): risk MEDIUM → HIGH, surface area churned by workspace-foundation; submit FIRST despite higher rebase cost - T5 (fingerprinting): submit IN PARALLEL with T1 (independent, no workspace coupling) - T3 (orchestration hints): risk MEDIUM → LOW, submit AFTER T1 lands - T2 (verify/archive phases): DEFERRED — overlaps slice 6 workspace-verify-and-archive proposal - T4 (pipeline runner): DEFERRED — overlaps slice 5 workspace-apply-repo-slice proposal; apply semantics being redefined Section 0.5 records the 2026-05-04 sync merge (fork PR #12). Constraint: spec-driven schema validation fails (no deltas) — acceptable, this is a planning umbrella, not a capability change Confidence: high (analysis based on reading all 4 workspace slice proposals on upstream/main) Scope-risk: narrow (fork-only docs, never contributed) Reversibility: clean Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Adds the long-tracked umbrella change
openspec/changes/upstream-contribution/that maps fork's 26 commits to a 5-PR upstream contribution plan. Originally drafted 2026-04-17 (memoryproject_openspec_upstream_strategy.md), updated 2026-05-04 to account for upstream's workspace-foundation landing (PR Fission-AI#1045) and TabishB's 21-day silence since the 2026-04-13 PR Fission-AI#891 ack.Key Revisions
workspace-verify-and-archiveworkspace-apply-repo-sliceWhy Submit a PR Instead of Push to main
This is fork-internal planning docs (never goes upstream), but the commit affects strategy decisions that future contributors / agents will reference. PR keeps the audit trail consistent with sync PR #12.
Test plan
node bin/openspec.js validate upstream-contribution --strict— fails on "no deltas" because this is a planning umbrella, not a capability change. Pre-existing condition since 2026-04-17 draft. Acceptable.🤖 Generated with Claude Code