Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BunsDev wants to merge 1 commit into from
+6 −6
Closed

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions tests/conformance/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Familiar Contract v0.2 Conformance Suite
# 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.

Run the full suite from the repository root:

Expand All @@ -10,4 +10,4 @@ bash tests/conformance/run-conformance.sh

Convention: `positive/<n>-<name>/` cases should PASS when run with `node validators/validate.js <case>`. `negative/<n>-<name>/` cases should FAIL for the documented reason in that case's `CASE.md`.

A claim of v0.2 compliance = passing every positive case and failing every negative case.
A claim of v0.3.0 compliance = passing every positive case and failing every negative case.
2 changes: 1 addition & 1 deletion tests/conformance/negative/09-missing-memory/CASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# 09 Missing MEMORY.md

Violated property: Persistent Memory. Validator check: `checkMemory` should reject this because `MEMORY.md` is absent, but the current implementation reports it as a warning only. Expected behavior for v0.2 conformance: `node validators/validate.js <case>` exits non-zero with an error pattern like `MEMORY.md does not exist`.
Violated property: Persistent Memory. Validator check: `checkMemory` rejects this because `MEMORY.md` is absent (promoted from warning to violation in v0.2.0; RFC-0001 §3.4 makes file presence a MUST). Expected behavior: `node validators/validate.js <case>` exits non-zero with an error pattern like `MEMORY.md does not exist`.
4 changes: 2 additions & 2 deletions validators/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Validator — familiar-contract

A zero-dependency Node.js CLI that checks a familiar directory for familiar-contract v0.1.0 compliance.
A zero-dependency Node.js CLI that checks a familiar directory for familiar-contract v0.3.0 compliance.

## Requirements

Expand Down Expand Up @@ -44,7 +44,7 @@ node validate.js --help
## Output

```
familiar-contract validator v0.1.0
familiar-contract validator v0.3.0
Checking: /path/to/familiar

Property Coverage:
Expand Down