Skip to content

docs: align public launch positioning#1

Open
pboling wants to merge 1 commit intomainfrom
chore/public-launch-alignment
Open

docs: align public launch positioning#1
pboling wants to merge 1 commit intomainfrom
chore/public-launch-alignment

Conversation

@pboling
Copy link
Copy Markdown
Contributor

@pboling pboling commented May 4, 2026

Summary\n- aligns public README/site language with the StructuredMerge launch model\n- removes product/product-boundary phrasing from public guidance\n- keeps the copy focused on shared specs, fixtures, conformance evidence, and peer implementation surfaces\n\n## Verification\n- git diff --check\n- targeted copy audit for product-boundary/separate-product language\n

Copilot AI review requested due to automatic review settings May 4, 2026 08:11
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository README to match the public StructuredMerge launch positioning, emphasizing the shared spec/fixtures model and linking to the main project resources.

Changes:

  • Refreshes README positioning to describe this repo as the Ruby implementation of the StructuredMerge contract alongside peer language implementations.
  • Adds links to structuredmerge.org, the spec repo, and the shared fixtures repo.
  • Updates Conformance/Development/Status sections to reflect shared-fixtures-driven validation and common repo tasks.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md

## Conformance

Integration tests should consume the shared fixture corpus from the sibling `../structuredmerge-fixtures` checkout. A ruleset, fixture, diagnostic shape, or review outcome should mean the same thing whether exercised through Go, TypeScript, Rust, or Ruby.
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.

2 participants