Getting help

Found a bug or missing behavior?

Open an issue on the repository: github.com/agustinusnathaniel/klyro/issues.

To make an issue actionable, include:

• the command you ran and its exit code (see the exit-code table);
• your klyro.yaml, with every secret value removed: names only;
• for unexpected defects, a run with KLYRO_VERBOSE=1 to capture details;
• the Klyro version (klyro --version) and Node version.

Questions while building

• The quickstart covers the full first-stack walkthrough.
• The klyro.yaml reference lists every supported field and value.
• Limitations states plainly what v0.1 does not do, before you file a “missing feature” report.

Contributing changes

• Architecture overview: package ownership and Effect boundaries.
• Providers: how new runtime and integration support is added.
• Upgrading: the controlled procedure for toolchain bumps.

Security-sensitive reports are best raised through a private channel with the maintainers rather than a public issue; when in doubt, omit secrets and describe the impact instead.