[pull] master from SchemaStore:master#494
Merged
Merged
Conversation
* Add Agent Permission Policy schema (.agents/permissions.json) * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
* Added schema abc-supply-plan-13.0.0.json - Added abc-supply-plan-13.0.0.json schema file - Updated catalog.json to include version 13.0.0 and set as default - Updated schema-validation.jsonc with validation configuration - Added positive test case for version 13.0.0 - Copied negative test cases from version 12.0.0 with updated schema references Key changes in version 13.0.0: - Added required sourceLink property to demand row metadata (oneOf: null, Clinical Demand Forecast link, or Supply Plan link) Testing: - Validated schema-specific: node ./cli.js check --schema-name=abc-supply-plan-13.0.0.json - Validated full test suite: node ./cli.js check (802 schemas pass) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: Michael Osofsky <michael@abc-plan.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
* Added schema abc-clinical-demand-forecast-2.0.0.json - Added abc-clinical-demand-forecast-2.0.0.json schema file - Updated catalog.json to include version 2.0.0 and set as default - Updated schema-validation.jsonc with validation configuration - Added positive test case for version 2.0.0 with required dispensationIntervals/dispensationIntervalUnit fields - Copied negative test cases from version 1.0.0 Key changes in version 2.0.0: - Added required dispensationIntervals (non-empty array of numbers >= 1) on dosingRegimenDefinition - Added required dispensationIntervalUnit (enum: days/weeks/months/years) on dosingRegimenDefinition Testing: - Validated schema-specific: node ./cli.js check --schema-name=abc-clinical-demand-forecast-2.0.0.json - Validated full test suite: node ./cli.js check (all 802 tested schemas pass) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Added schema abc-clinical-demand-forecast-3.0.0.json - Added abc-clinical-demand-forecast-3.0.0.json schema file - Updated catalog.json to include version 3.0.0 and set as default - Updated schema-validation.jsonc with validation configuration - Added positive test case for version 3.0.0 - Copied negative test cases from version 2.0.0 Key changes in version 3.0.0 (breaking): - Replaced dosingFrequency string enum (once_daily_qd, twice_daily_bid, every_other_day, etc.) with a structured DosingFrequency object that supports multi-phase regimens. Each DosingFrequency has a description (also used as the AI generation prompt) and an ordered phases array (1-10 phases). Each DosingPhase defines a repeating cycle via cycleDoses and cycleUnit (days or months), and a repeat duration via repeatFor and repeatForUnit (days, weeks, months, or years). repeatFor: 0 marks a terminal phase that runs for the remainder of the treatment. This enables regimens such as capecitabine 14-on/7-off and "weekly for 6 weeks then monthly" that the old flat enum could not express. - Positive test data updated: replaced the old once_daily_qd string with an equivalent single terminal-phase DosingFrequency object (cycleDoses: [1], cycleUnit: days, repeatFor: 0). Testing: - Validated schema-specific: node ./cli.js check --schema-name=abc-clinical-demand-forecast-3.0.0.json (PASS) - Validated full test suite: node ./cli.js check (PASS, all 803 tested schemas) Stacked-branch note: this branch was created from feature/publish-abc-clinical-demand-forecast-2.0.0 (not master) because the 2.0.0 PR has not yet been merged upstream. When the 2.0.0 PR merges, rebase this branch onto master before merging. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: Michael Osofsky <michael@abc-plan.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
* Add PRML manifest schema
PRML — Pre-Registered ML Manifest — is an open CC BY 4.0 specification
for committing machine-learning evaluation claims to a SHA-256 hash
before the experiment runs.
The schema validates the eight required PRML v0.1 fields plus optional
v0.2 RFC additions (streaming variant, runner attestation, revocation).
File patterns target *.prml.yaml, manifest.prml.yaml, and the
prml-manifest.{yml,yaml} convention.
Both schema versions are JSON Schema 2020-12 conformant and validated
against 32 locked conformance vectors (12 v0.1 + 8 v0.2 + 12 v0.1
inputs against v0.2 schema for backwards-compat). Detail at
https://spec.falsify.dev/schema/.
Spec author: Studio 11 Turkey Ltd. Şti. (hello@studio-11.co).
v0.1 stable; v0.2 RFC freeze 2026-05-22 23:59 UTC.
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
---------
Co-authored-by: Studio 11 <hello@studio-11.co>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
* Add memnex schema memnex is an open specification for portable meeting outputs (transcripts, summaries, action items, decisions) from local-first processing tools. Spec: https://github.com/UladzKha/memnex Reference implementation: https://www.npmjs.com/package/memnex-spec * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )