docs: reconcile RFC coordination index with shipped reality - #1349
Merged
Conversation
… guidelines Phase B (foundation-corpus write path), Component/Token Relationships, and the guideline entity had all shipped without the coordination index or its sibling docs catching up, so the "living index" no longer matched reality. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: ec5f852 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
- rfc-coordination.md, token-studio-sunset.md: beads IDs 122/459 were mistakenly linked as GitHub issue URLs, which resolve to an unrelated auto-generated release PR; unlinked them (beads have no GitHub issue). - agent-surface.md: promote write_token to NORMATIVE (MUST), matching authoring-workflow.md now that the Phase B write target has shipped. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Run report for ec5f8522Total time: 139.9ms | Comparison time: 110.7ms | Estimated loss: 29.2ms (20.8% slower)
Changed files |
Contributor
🎨 Token Changes ReportTokens Changed (0)Original Branch: This comment was automatically generated by the token diff tool. 🤖 |
Contributor
🧩 Component Schema Changes ReportNo component schema changes detected.This comment was automatically generated by the component schema diff tool. 🤖 |
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.
Description
Reconciles
docs/rfc-coordination.md(the RFC "living index") and its two siblingdocs with what has actually shipped, and updates the five GitHub RFC discussions
whose status blockquotes had drifted out of sync with the index.
docs/rfc-coordination.md: flip Phase B (foundation-corpus write path) from"next open gate" to shipped (epic
spectrum-design-data-122, closed); addRFC-E (Component/Token Relationships) and RFC-F (Guidelines/Phase 10) rows; add
a draft-RFC row for [DRAFT RFC] Platform Coverage Metrics via Manifest Adoption #1324; reference 6 previously-orphaned spec files; refresh
the Token Taxonomy, Vocabulary, and Formatting — Naming Convention Decomposition #806/[DRAFT RFC] Token Deprecation and Consolidation #623/[DRAFT RFC] Token Authoring Workflow and Process #625/[RFC-A] Component Contract in Design Data Spec #832 rows with rules and PRs shipped since the last update.
packages/design-data-spec/spec/authoring-workflow.md: flip Phase B (tokenlifecycle ops, mode-set management) from "not yet shipped" to shipped; clarify
write_componentremains unscheduled (out of Phase B's scope).docs/token-studio-sunset.md: mark Phase 1 (foundation-corpus write target)done, unblocking Phase 2.
dated
Status:blockquote to match the refreshed index, per the doc's own rulethat the index and discussions move together.
Related Issue
N/A — documentation reconciliation, not tied to a single issue.
Motivation and Context
The coordination doc is meant to be updated in the same PR that lands a change,
but several months of shipped work (Phase B, CTR, guidelines) had landed without
it, leaving the index unable to be trusted as an entry point. This makes the
three docs and the five affected discussions consistent with shipped reality
again.
How Has This Been Tested?
node tools/changeset-linter/src/cli.js check --fail-on-warningspasses.packages/design-data-spec/spec/*.mdis referenced bythe coordination doc.
SPEC-XXXid cited in the doc exists inrules.yaml.actual cascade write-path code (
sdk/core/src/write.rs, CLI/TUI/MCP callsites) before flipping any status language.
Screenshots (if appropriate):
N/A
Types of changes
Docs-only change (patch changeset for
@adobe/design-data-spec).Checklist: