Implementation progress
Updated: October 14, 2026. Current development version: 0.3.0-dev.
October 14 language upgrade
- Recoverable runtime errors, throw/rethrow, structured Error values, call stacks, and cancellation/depth boundaries that cannot be swallowed by catch.
- Enforced variable/parameter/result contracts, nullable values, nominal immutable record fields, enums, and static checking of known contracts across imports.
zy.jsonmanifests, isolated named tests, and locked local package snapshots.- IPv6 parsing/splitting/allocation and exact CIDR set operations.
- Bounded outgoing HTTP, atomic text writes, UTC time, and cryptographic helpers.
- Typed record/signature editor features, document-local references and private rename, syntax/snippets, and installed bundled extension version 0.3.0.
- A complete network-validator application with reusable models/rules, human/JSON findings, valid/invalid fixtures and four isolated tests.
Local validation passed: Go tests/vet, frontend/contract/formatter/server
regressions, extension grammar/client tests, release-tool tests, and a 3-second
type-checker fuzz run (17,102 inputs). The separate backend passed entry/worker
checks and four unit tests through the installed zy command. New database-error
handler behavior is covered with an isolated fake store; a new live MongoDB or
real VS Code extension-host integration run is not claimed for this update.
See performance for the measured local baseline.
Completed engineering work
| Roadmap area | Implementation |
|---|---|
| Reliable integers | Exact arithmetic, checked overflow, precise comparisons, finite math/conversions, literal validation |
| Networking | Counted bounded splitting, /0 and final-address boundaries, normalized equality, variable-size allocation |
| Runtime audit | Overflow-safe ranges, control-flow context checks, safe slices/sorts, arity checks, identity equality, cycle display, call/parser limits |
| Host integration | Injected I/O, output-error propagation, script arguments, cooperative cancellation |
| Local library | Read-only files, JSON, environment, paths, IPv4 parsing and allocation |
| Useful workflows | Inventory checker, subnet planner, configuration validator; human/JSON output and failure exits |
| Initial CLI tooling | Run/check/help/version, documented exit codes, deadline option, legacy invocation retained |
| Local modules | File-relative imports, explicit live exports, isolated scopes, shared dependency cache, complete preflight, cycle/source limits, source-origin diagnostics |
| Formatting | Lossless inline spacing, block/statement layout and indentation; stdout/write/check modes; token/structural guards; prepared replacement and concurrent-edit checks |
| Editor preview | VS Code syntax/snippets plus opt-in trusted-workspace language client, with locked tokenizer/client tests |
| Language server | Stdio protocol, unsaved overlays, UTF-16 diagnostics, formatting, lexical hover/completion/definition, cancellation, coalesced validation and stale-result protection |
| Diagnostic contract | check --json, schema 1 output, stable category codes, source-free interchange, Unicode coordinates |
| Release engineering | Six-platform archive builds, version injection, build metadata, checksums, clean/tag gates, native package smoke tests and artifact workflow |
| Documentation | Decisions, migration guide, standard-library reference, workflow cookbook, updated status/README |
| Verification | Boundary/termination tests, CLI integration, valid/invalid workflow fixtures, deterministic reports, tutorial snapshots, documentation links/snippets |
Current engineering batch
Runtime responsibilities now live in separate value, environment, evaluation, member, and built-in files under regression coverage. Semantic requests use scope-aware symbols and unsaved dependency snapshots. Local tests/vet/build and compiled semantic smoke tests pass; core coverage is 74.3%, CLI 79.6%, and LSP 83.1% at this batch validation. Formatter fuzzing completed 732,024 and then 403,841 executions after the layout changes; a numeric member-access regression is retained in the corpus.
Real Windows VS Code 1.141.0 extension-host tests and light/dark visual review passed. The JSON automation walkthrough led to a clearer assertion hint and a JSON-first quickstart. The review record separates engineering evidence from pending human feedback. CI is expanded to six native OS/architecture targets, including Linux and Windows ARM64 and Intel macOS. The manual artifact workflow executes all six cross-built archives on matching hosts. The 15-job native/test/tooling run passed on f696d3b, including Linux/Windows ARM64, macOS on both architectures, Go 1.22 compatibility, Linux race detection, and real VS Code 1.85.2 integration. The six-target cross-built archive run also passed all matching-host executions on the same runtime implementation (before the test-fixture-only canonical-path correction). Editor feature fuzzing completed 210,440 executions with no failures.
Earlier validation and acceptance gates
Local validation passed on Windows with Go 1.26.0:
go test ./... -count=1 -timeout=60s -cover: all tests passed; CLI coverage 78.3%, core coverage 72.4%, language-server coverage 82.7% at the language-server validation run.go vet ./..., Go formatting, andgit diff --checkpassed.- Minimum-version validation: Go 1.22.12 Windows tests and vet passed.
- Windows executable build and compiled module run/check, formatter replacement, and formatter exit-code checks passed. Earlier compiled-CLI failure-report/exit-code checks passed for all three workflows.
- Formatter fuzzing: 514,179 executions in the final five-second run, no failures; valid inputs must format successfully and remain idempotent.
- Earlier frontend fuzzing: 90,208 executions in five seconds, no failures.
- Earlier JSON fuzzing: 96,561 executions in five seconds, no failures.
- Linux and macOS amd64 executable, CLI-test, and core-test cross-compilation passed for the updated source. These verify compilation, not native execution.
- Six platform archive builds completed: Windows, Linux, and macOS on amd64 and arm64. The Windows amd64 archive passed checksum verification and clean-directory execution of modules, JSON diagnostics, formatting, and success/failure fixtures for all three workflows.
- A separate linker-injected build correctly reported
0.2.0-rc.1; the normal local build still reports0.2.0-dev. - Five Python packaging tests passed, including deterministic archive layout, executable permissions, stable-tag gates, checksum failure, and unsafe-path rejection.
- Five Node editor tests passed using locked dependencies, including real TextMate/Oniguruma grammar tests and mocked client lifecycle/trust checks; no VS Code visual review or Marketplace publication was performed.
- The compiled Windows stdio server passed initialize/shutdown/exit, UTF-16 error positions, unsaved-document edits, diagnostic clearing, and formatting with an empty PATH.
- Protocol framing fuzzing completed 479,255 executions in five seconds with no failures. Server tests also cover dependency overlays, close/disk fallback, watched-file changes, stale results, cancellation, message limits, and malformed input.
The regression suite also checks collection bounds, dependency graph limits (including cached subgraphs), module identity/isolation, dependency/closure diagnostics, formatter token preservation, concurrent-edit rejection, and runnable module examples. Coverage percentages are snapshots; use the README commands to reproduce current values.
CI is configured for Windows, Linux, and macOS on Go 1.22 and stable Go, plus native packaging smoke tests and editor grammar tests. A manual artifact-build workflow is configured with Go 1.26.0. The original nine hosted jobs passed before this batch; newer matrix results must be checked in Actions. Linux/stable includes the race detector; the local Windows environment has CGO disabled and no discovered GCC, so local race validation is unavailable. ARM64 archives are cross-built and have not been executed locally.
The engineering portion of roadmap milestones 1 and 2 is implemented. Full usability acceptance remains pending trials with at least three general automation users. No messages or invitations were sent to others.
Milestone 3 now includes local modules, conservative formatting, editor/client support, language-server diagnostics/formatting, JSON diagnostics, and archive/version tooling. The latest formatter expands statement layout and lexical semantic editor features are implemented; public distribution remains open. The Windows executable is available locally at bin/zy.exe; archive outputs are under ignored dist/. No release has been published. Local development packages explicitly record an uncommitted/dirty source state.
Remaining roadmap work
- Dynamic member/type inference, rename/references, additional accessibility/theme review, and editor distribution.
- Decide public distribution, publisher identity, and signing/notarization; native six-target execution is verified.
- Finer-grained diagnostic codes beyond stable categories, and broader grammar/conformance coverage.
- Optional live provider integration, contingent on workflow evidence and provider requirements.
- Human usability review using the prepared trial protocol, and permanent branding clearance.
These are subsequent stages, not features included in this development build. See the roadmap for dependencies and acceptance criteria.