GoWDK

Write or update a GOWDK pull request title/body. Use for local branches or GitHub PRs that need a concise why/what/verification summary, issue links, migration notes, and generated-output or docs impact.

Bump the GOWDK release version. Use when updating the CLI version, VS Code extension package version, install snippets, release docs, release notes, or validating a 0.x release metadata change.

Write or update GOWDK documentation across product, engineering, language, compiler, reference, onboarding, examples, and agent guidance.

Change GOWDK language syntax or semantics. Use for parser, formatter, lexer, analyzer, diagnostics, `.gwdk` metadata, `view {}` markup, guards, routes, layouts, actions, APIs, `build`, `server`, `paths`, or docs/examples for language behavior.

Review GOWDK code changes, a PR, or a subsystem for correctness and maintainability. Use for code review requests, pre-merge checks, or auditing a diff against GOWDK product and contract rules.

Change GOWDK compiler internals without changing public language behavior. Use for AST shape, analyzer passes, IR (`gwdkir`) structure and invariants, lowering, diagnostics registry plumbing, validation order, or compiler performance work.

Change GOWDK build output, generated Go app source, generated routes, manifests, CSS/assets, SSR handlers, action/API adapters, fragments, guards, or runtime/appgen/buildgen contracts.

Diagnose and fix a GOWDK bug report, failing command, broken example, compiler diagnostic regression, generated output mismatch, or CI failure tied to this repository.

Plan and build a new GOWDK feature or substantial capability, from spec to verified vertical slice. Use for new user-facing behavior, new compiler/runtime capabilities, or large changes that need a feature spec and implementation plan.

Simplify or reorganize GOWDK code without changing behavior. Use for deduplication, removing indirection, splitting or merging packages, renaming internals, or cleanup that should leave tests and public contracts untouched.