Zy documentation

Start with getting started, then run the tutorials. Use the language reference while writing scripts.

Using Zy today

Getting started: build, run, first program, troubleshooting.
Automation quickstart: JSON validation for general automation users.
Language reference: syntax, types, built-ins, networking.
Types and errors: contracts, records, enums, nullable values, try/catch.
Projects and tests: manifests, isolated tests, locked local packages.
Network validator: explained IPv4/IPv6 policy findings.
Tutorials: short programs with expected output.
Practical workflows: runnable validation and planning tasks.
Standard library: local file/JSON/environment/path/network APIs.
Local modules: shared policies, imports, exports, and scope.
CLI tooling: formatter, dependency checks, and exit codes.
HTTP servers and MongoDB: serve command, route handlers, authentication, and database APIs.
Backend services: prepared execution, sessions, roles, queries, transactions, migrations, workers, cache, metrics, and traces.
Editor support: VS Code syntax and opt-in language client.
Language server: unsaved diagnostics, formatting, setup, protocol, and limits.
Diagnostics: JSON check results and stable category codes.
Release guide: install archives, build packages, and verify checksums.
Migration guide: behavior changes in 0.2.0-dev.
Status and limitations: capabilities and known issues.

Architecture: pipeline and source responsibilities.
Improvement plan: proposed reforms and milestone gates.
Implementation progress: completed work and remaining gates.
Usability trials: prepared task protocol and observation template; trials pending.
Engineering review: completed visual/automation walkthrough and remaining participant feedback.
Numeric semantics and runtime bounds: implemented decisions.
Modules and formatting: implemented tooling decision.
Contributor guide: workflow and checks.
Changelog: recorded changes.
Social media copy: ready-to-use project introduction.
Historical proposals: early ideas, not the specification.

Runtime changes should update the reference and examples. Proposed APIs belong in design documents until implemented and verified.