[leftibot]

The schema practices (#85, #86, #87, #88) and the last row of #92: four changes, reviewed and merged one by one as a stack on leftibot/project_validator (its PRs #63 to #66), brought here as one. Each landed with every gate green: the full suite, 99% branch coverage, ruff, mypy, lizard, jscpd and the strict self-check.

The profile

Tabular data (#92): Frictionless Data Packages, a format (Data Package) recognised by intent: a datapackage.json or .yaml, a tableschema.json, or a JSON or YAML file whose $schema or profile names a Data Package profile; a CSV alone makes nothing. schema-validation: frictionless validate (and the frictionlessdata/frictionless-ci action), goodtables, csvlint with a schema. A dvc.yaml alone shows data versioning, not a schema to validate against, and large-files already honours DVC, so it recognises nothing; the issue listed it, and the docs page says why not.

The checks

Check	Kind	Passes when	Otherwise
schema-declared	facts (facts/declaration.py: a Declares per format, SchemaDeclaration facts read at extraction)	every schema declares its dialect and identifier: $schema and $id; an openapi/asyncapi version and info.version; an XSD's targetNamespace; a .proto file's syntax and package; a descriptor's profile and name	fails, listing what each leaves out; a superseded dialect (a JSON Schema draft before 2019-09, Swagger 2.0) warns; a test suite's schemas are reported, not judged
schema-examples	tools (aspect examples)	CI checks the schemas' examples: ajv test --valid/--invalid, a validator run on an examples directory (check-jsonschema, jv, xmllint, jing), a linter whose rules validate a description's examples (spectral, redocly, vacuum), contract tests (schemathesis, dredd)	warns
schema-compatibility	tools (aspect compatibility)	CI checks the schemas for breaking changes against the main branch or a registry: json-schema-diff, oasdiff breaking (and its action), openapi-diff --fail-on-incompatible, buf breaking (and buf-action)	warns

A validator that also checks examples or breaking changes is one tool (combined), as the API linters already were. Formats no tool serves for a practice are not asked.

What else moved

• The content probes of JSON Schema and Data Package read a top-level key only (^(?:\{\s*)?\s{0,4}"$schema"): a document quoting a schema is no schema. This validator's own facts snapshots, which now record declared $schema values, had made the repository a JSON Schema project in the strict self-check.
• The well-configured XML fixtures gain a targetNamespace their documents, stylesheet (xpath-default-namespace) and XSpec follow; the Data fixture's XSD now describes the document beside it (its item had attributes the schema did not allow).
• The JSON Schema, XML schemas, Data and OpenAPI fixtures gain examples and the CI steps that check them and diff the schemas; the bare JSON Schema and Data Package fixtures lose their identifiers.
• README rows for the three checks, each profile's page, the architecture's aspect list and Declares, history item 13.

What the issues still list beyond this: #86's xsi:schemaLocation on documents; #92's SQL migration-safety check and the later large-files note (already honoured). The user decides what to close.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.77%. Comparing base (28bdbbc) to head (37cb4bb).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main     #178    +/-   ##
========================================
  Coverage   99.76%   99.77%            
========================================
  Files         251      258     +7     
  Lines       13276    13560   +284     
  Branches     1475     1495    +20     
========================================
+ Hits        13245    13529   +284     
  Misses         31       31            

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.