Skip to content

refactor(dialects): fold the evidence directory into fixtures - #29

Merged
soulbah merged 1 commit into
devfrom
refactor/dialect-support-files
Oct 10, 2026
Merged

soulbah merged 1 commit into
devfrom
refactor/dialect-support-files

Conversation

@soulbah

@soulbah soulbah commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Change

dialects/ now holds the official Dialects, their metadata files and one fixtures/ directory. The evidence/ directory is gone:

  • The three kinds of file that validation reads move unchanged: each Dialect's reviewed scenarios from evidence/<dialect>/scenarios.json to fixtures/expectations/<dialect>.json, the plan fixture inventory to fixtures/inventory.json, and the provider registry equivalence to provider-registry-equivalence.json, beside dialects.json.
  • The research snapshots recorded while the Dialects were first written (coverage matrices, rule audits, provider baselines and source inventories, terminology and catalog snapshots, spike notes) are removed. No script generated, read or refreshed them, and several no longer matched the sources they describe; the Dialect sources, their fixtures and the generated provider coverage reference describe the current state. Git history keeps them.

Support files stay outside the Dialect directories, which keep only what rootform package publishes. The validator now accepts, beside the fixture directories, only the inventory and one expectations file per official Dialect; it checks that every scenario names an existing fixture and that the inventory and the expectations name declared Rules. Dialect sources, fixtures and goldens are unchanged, so the embedded release set and every analysis stay identical.

Validation

  • bun run check: 306 tests pass; repository and Dialect structure valid.
  • bun scripts/ci/run.ts dialects scenarios with the reference runtime 0.1.0-pr.117.1: 96 planned fixtures replay, every scenario expectation holds against its golden with none naming an unplanned fixture, and the Playground inputs, Forms and nine pinned renderer inputs reproduce.
  • An expectation that names a Rule absent from its fixture makes Dialect verification fail on that scenario, so verification reads the expectations from their new place.
  • The validator rejects a stray file in fixtures/, an expectations file for an unknown Dialect and a top-level evidence/ directory.

- Move each Dialect's reviewed scenarios to fixtures/expectations and the
  plan fixture inventory to fixtures/inventory.json, unchanged.
- Move the provider registry equivalence beside dialects.json.
- Remove the research snapshots and spike notes that no script generates,
  reads or refreshes; git history keeps them.
- The validator accepts only the inventory and one expectations file per
  official Dialect beside the fixtures, and checks their fixture and Rule
  references.
@rootform-contribution-delivery

rootform-contribution-delivery Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Contribution progress

Source: 0eb9c00e4000d8fe1eb9e50e2574f07cae36eaaa

Selected validations: docs, cli, dialects, policies, examples, distribution, tooling, generated. Repository safety always runs.

Stage Status
Public validations Passed (checks)
Documentation preview Passed (open preview)
Development integration Passed
Staging sites Passed
Release Included in v0.2.1

Applicable consumers are synchronized on their development branches and the staging sites. Releases are published from main; the Release row follows them.

@soulbah
soulbah merged commit b6cfe4f into dev Oct 10, 2026
10 of 11 checks passed
@soulbah
soulbah deleted the refactor/dialect-support-files branch October 10, 2026 21:55
@soulbah

soulbah commented Oct 10, 2026

Copy link
Copy Markdown
Contributor Author

/rootform retry

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.

1 participant