Engineering and usability review
Reviewed October 12, 2026, for general automation users, as selected by the maintainer. These are engineering observations, not participant research or adoption evidence.
Completed walkthrough
- Ran the configuration validator against its valid fixture: readable PASS report and exit 0.
- Ran the invalid fixture: four field/rule/correction messages, assertion summary, and exit 1. Existing regression checks cover JSON output and deterministic reports.
- Checked shared-module navigation and unsaved changes through a real VS Code extension host: exported definitions update without saving, and private bindings are excluded from the Zy provider.
- Applied formatting through VS Code’s real command API, then introduced and removed a syntax error: diagnostics appear and clear without executing the script.
- Visually inspected VS Code 1.141.0 on Windows in an isolated profile using Dark Modern and Light Modern. Comments, strings, keywords, punctuation, status registration, indentation, and
json.loadhover text were readable. Format Document expands inline blocks. Screenshots remain local under ignoredoutput/playwright/. - Real extension-host tests additionally cover completion, parameter hover, import definition, diagnostic clearing, and shutdown. The runner uses temporary settings/workspace/extensions; normal user settings are untouched.
Findings and changes
| Observation | Change or follow-up |
|---|---|
| Original introduction emphasized networking before general automation | Added a JSON-first automation quickstart and broadened the README introduction |
| Failed assertions inherited an argument-count/type hint | Assertions now point to their failed condition and supplied message |
| Dense one-line blocks were difficult to scan | Formatter expands blocks and separates statements, with token/structure preservation tests |
| Long validation calls run beyond a narrow editor viewport | Documented Alt+Z word wrap; automatic call wrapping is pending multiline-argument grammar support |
| VS Code word suggestions can include words outside lexical scope | Documented the distinction; provider tests disable editor word suggestions to validate only Zy results |
| Early documents incorrectly described already-passed native CI as pending | Updated current status and separated configured coverage from recorded run evidence |
This review does not establish accessibility across all themes, hardware, or assistive technologies. Permanent logo/name clearance and extension distribution are separate tasks.
Native validation evidence
- Go Tests: all 15 jobs passed, source
f696d3b: all six native OS/architecture targets, Go 1.22 compatibility, Linux race detection, real VS Code integration, grammar tests, and native-built archive smoke checks. - Build release artifacts: package plus all six native jobs passed, source
f0f17c3: the cross-built archives executed on matching amd64/arm64 hosts for Windows, Linux, and macOS. The subsequent source correction changes only test fixture path canonicalization. - These are unsigned development artifacts, not a published release.
Human review still required
No external participants have been contacted. Run the trial protocol with at least three general automation users, including someone learning scripting. Record actual commands, assistance, comprehension, and whether Zy improves a task they already perform. Do not substitute automated test results or this engineering walkthrough for those observations.
The next decision should follow repeated user friction: editor setup, error comprehension, script reuse, or input/output handling. Live integrations and additional syntax should depend on that evidence.