Versions and Diagnostics¶

@meta.syntax declares language syntax, not package, policy, registry, or organization version.

Syntax Versions¶

Use the minimum required version for reusable published fragments. Use current syntax for new project entry files.

Operation semantics follow the complete reachable composition graph. An inherited, imported, inline-composed, or extension-carried source declaring 1.5.0 enables declaration order for the graph even when the entry file declares an older version. Inline @use declarations inside @extend bodies are included. PS018 reports that mixed-version requirement; it does not reject the composition.

Upgrade Commands¶

# Preview all .prs version changes.
prs upgrade --dry-run

# Upgrade syntax declarations using per-file atomic replacement.
prs upgrade

# Find compatibility and shape problems.
prs validate --strict

# Preview generated output and hook migration.
prs compile --dry-run

prs upgrade parses every discovered file before writing, so an initial parse failure aborts the complete plan. Each file then uses atomic replacement and preserves permissions. Multi-file upgrade is not transactional: a write-time failure in a later file does not roll back files already replaced. Symlinks are skipped. Run upgrades on a clean version-control branch.

Model Versions¶

@meta.syntax does not track AI models. Agent and skill model values resolve against the model catalog configured under models. Floating aliases such as sonnet follow the newest release in the catalog, and the Model Catalog lists every built-in model. PS041 reports pinned models that are deprecated or retired, together with their replacement, models outside models.supported, and inconsistent models.profiles entries.

Key Diagnostics¶

Release Gate¶

prs validate --strict
prs compile --dry-run
prs diff --all

Commit syntax upgrades, lockfile changes, source changes, and reviewed generated outputs together according to repository policy.

See Upgrade 1.15 to 1.16 for release-specific migration steps.