Skip to content

docs: sweep stale version claims in conformance/validator docs#5

Closed
BunsDev wants to merge 1 commit into
mainfrom
docs/conformance-version-sweep
Closed

docs: sweep stale version claims in conformance/validator docs#5
BunsDev wants to merge 1 commit into
mainfrom
docs/conformance-version-sweep

Conversation

@BunsDev

@BunsDev BunsDev commented Jul 22, 2026

Copy link
Copy Markdown
Member

Summary

Post-merge code review of 65622c0..710036e (RFC-0001 v0.3.0, PR #3) found current-version claims the sweep missed — the CHANGELOG sweep list (README.md, rfcs/README.md, SPEC.md, docs/faq.md, validate.js) omitted these files:

File Was Now Severity
tests/conformance/README.md titled/defined the suite as v0.2 compliance v0.3.0 Medium — RFC §6.1 defines this exact 10-case suite as the v0.3.0 conformance criterion, so the suite's own README contradicted the RFC
validators/README.md claimed v0.1.0 compliance + stale sample output v0.3.0 Low, pre-existing — two bumps behind the binary it documents
negative/09-missing-memory/CASE.md said missing MEMORY.md "is a warning only" states the v0.2.0 warning→violation promotion Low, pre-existing — false since v0.2.0 (CHANGELOG:58); case 09 fails correctly today

Verification

  • Docs only — validators/, fixtures, schemas untouched by this diff
  • bash tests/conformance/run-conformance.sh: 5/5 positive + 10/10 negative, READY
  • CASE.md expected error pattern re-checked against actual validator output (MEMORY.md does not exist)
  • Residual-sweep grep over the three files: zero stale current-version claims remain

Refs coven-threads bead threads-auu (review findings recorded there). Follow-up to #3.

Post-merge code review of 65622c0..710036e found current-version claims
the v0.3.0 sweep missed (CHANGELOG sweep list omitted these files):

- tests/conformance/README.md: suite titled/defined as v0.2 while RFC-0001
  §6.1 defines this exact suite as the v0.3.0 conformance criterion (Medium)
- validators/README.md: claimed v0.1.0 compliance + stale sample output,
  two bumps behind the binary it documents (Low, pre-existing)
- negative/09-missing-memory/CASE.md: said missing MEMORY.md 'is a warning
  only' — false since v0.2.0 promoted it to a violation (Low, pre-existing)

Docs only; validator and fixtures untouched. Suite re-verified:
5/5 positive + 10/10 negative, READY. Refs coven-threads bead threads-auu.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 22, 2026 03:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates documentation under the conformance suite and validator docs to remove stale “current version” claims and align stated compliance level with RFC-0001 v0.3.0.

Changes:

  • Bump validators/README.md stated compliance/output from v0.1.0 → v0.3.0.
  • Bump tests/conformance/README.md suite title/definition from v0.2 → v0.3.0.
  • Update tests/conformance/negative/09-missing-memory/CASE.md to reflect the v0.2.0 warning→violation promotion and current expected validator behavior.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
validators/README.md Updates stated validator compliance/output version to v0.3.0.
tests/conformance/README.md Updates suite version claims/definition to v0.3.0.
tests/conformance/negative/09-missing-memory/CASE.md Clarifies expected failure semantics for missing MEMORY.md and references the relevant RFC requirement.

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

# Familiar Contract v0.3.0 Conformance Suite

This directory is the testable form of the Familiar Contract: a set of fixture familiars that encode the five normative properties as executable validator expectations. It uses the current repository validator as the conformance oracle while documenting where v0.2 expectations are stricter than the current implementation.
This directory is the testable form of the Familiar Contract: a set of fixture familiars that encode the five normative properties as executable validator expectations. It uses the current repository validator as the conformance oracle while documenting where v0.3.0 expectations are stricter than the current implementation.
@BunsDev

BunsDev commented Jul 22, 2026

Copy link
Copy Markdown
Member Author

Superseded by v0.4.0 (f70c796): main independently re-swept tests/conformance/README.md and rewrote validators/README.md + validate.js, absorbing this PR's version-claim fixes at the new baseline. The one surviving fix — negative/09-missing-memory/CASE.md's false 'warning only' claim — carries into the v0.4.1 re-cut of PR #6. Bead: threads-auu.

@BunsDev BunsDev closed this Jul 22, 2026
@BunsDev
BunsDev deleted the docs/conformance-version-sweep branch July 22, 2026 04:18
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