deno-knowledge-patch

# Deno Knowledge Patch Use this skill to choose current Deno APIs, CLI flags, configuration, and compatibility behavior. Check the relevant topic reference before changing a project because several features were removed, restored, stabilized, or given new defaults. ## Working approach 1. Inspect `deno --version`, `deno.json` or `deno.jsonc`, `package.json`, `deno.lock`, workspace configuration, and the commands used by CI. 2. Open every reference relevant to the requested change. Follow the exact option names and stability gates documented there. 3. Treat a later version-attributed statement as superseding an earlier one only for the behavior it explicitly changes. 4. Preserve least-privilege permissions. Do not add `-A` merely to bypass a permission failure. 5. Keep manifest and lockfile changes together, and use frozen or CI installation modes when reproducibility matters. 6. Verify with the narrowest applicable built-in commands: `deno check`, `deno lint`, `deno fmt --check`, `deno test`, and the requested build or package command. ## Reference index | Reference | Topics | | --- | --- | | [Build, publish, and deploy](references/build-publish-and-deploy.md) | `deno compile`, bundling, transpilation, package tarballs, publication, and deployment | | [Dependencies and workspaces](references/dependencies-and-workspaces.md) | Manifests, registries, npm/JSR resolution, lockfiles, installs, updates, catalogs, and workspaces | | [Desktop and ecosystem](references/desktop-and-...