Adapt CLI to wdl.20260701.1 and audit findings

.claude/skills/wdl-deploy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wdl-deploy
-description: Deploy and manage Cloudflare Workers-style projects on the WDL platform via the `wdl` CLI (init, deploy, config explain, whoami, doctor, tail, secret, workers, delete, d1, r2, workflows). Trigger when the user asks to scaffold or deploy a Worker, inspect resolved CLI configuration, identify the active control token/principal, run diagnostics, tail live logs, configure KV / Queues / Durable Objects / Workflows bindings, manage D1 / R2 / secrets through `wdl`, or troubleshoot wdl CLI output. Works with `wrangler.toml` / `wrangler.jsonc` projects pinned to wrangler@^4.
+description: Deploy and manage Cloudflare Workers-style projects on the WDL platform via the `wdl` CLI (init, deploy, config explain, whoami, doctor, tail, secret, workers, delete, d1, r2, workflows). Trigger when the user asks to scaffold or deploy a Worker, inspect resolved CLI configuration, identify the active control token/principal, run diagnostics, tail live logs, configure KV / Queues / Durable Objects / Workflows bindings, manage D1 / R2 / secrets through `wdl`, or troubleshoot wdl CLI output. Works with `wrangler.json` / `wrangler.jsonc` / `wrangler.toml` projects pinned to wrangler@^4.
 ---
 
 # WDL CLI deploy skill
@@ -44,6 +44,19 @@ Open the relevant doc before answering:
 Each doc has a Chinese twin at `docs/<name>-zh.md`; both languages are
 authoritative, and agent-facing references use the English set.
 
+New Wrangler configs should use `compatibility_date = "2026-06-17"` unless a
+project feature requires a newer target or the operator gives a different
+target. WDL follows Wrangler config priority (`wrangler.json`, then
+`wrangler.jsonc`, then `wrangler.toml`). The control plane is canonical for
+unsupported runtime shapes such as unsupported workerd experimental
+compatibility flags and WDL-reserved injected module names; the CLI still
+fails fast for cheap local cases such as Python Workers modules, unmapped
+top-level or selected-env Wrangler runtime/deploy keys (`[site]`,
+`workers_dev`, `pages_build_output_dir`, `observability`, `limits`,
+`placement`, etc.), and
+ambiguous runtime `env` name collisions between `[vars]`, explicit bindings,
+and the implicit `ASSETS` binding.
+
 Never recommend setting `CONTROL_CONNECT_HOST` outside local development: it
 overrides the TCP target the admin token connects to (Host header + TLS SNI
 still track `CONTROL_URL`), and a stale value in a CI or production shell could

AGENTS.md

@@ -12,7 +12,8 @@ capability docs live in `docs/`, while `templates/AGENTS.md` and
 and AI agents. Example tenant projects live under `examples/` and pin
 `wrangler@^4`; the deploy bundling step expects v4, so keep new examples and any
 docs that recommend a wrangler version on v4. New Wrangler configs should start
-with `compatibility_date = "2026-05-31"` unless the WDL runtime moves again.
+with `compatibility_date = "2026-06-17"` unless a project feature requires a
+newer target.
 
 ## Build, Test, and Development Commands
 

CHANGELOG.md

@@ -1,5 +1,77 @@
 # Changelog
 
+## Unreleased
+
+### Changed
+
+- `wdl init`, examples, and docs now default new Wrangler configs to
+  `compatibility_date = "2026-06-17"` for the documented feature baseline.
+- `wdl deploy` now follows Wrangler config priority
+  (`wrangler.json`, `wrangler.jsonc`, `wrangler.toml`); the control plane
+  remains canonical for runtime/workerd bundle errors, while the CLI still
+  rejects cheap local cases like Python Worker modules and ambiguous runtime env
+  name collisions between `[vars]`, explicit bindings, and the implicit
+  `ASSETS` binding. Deploy also fails fast on unmapped Wrangler runtime/deploy
+  keys such as `[site]`, `workers_dev`, `pages_build_output_dir`,
+  `observability`, `limits`, and `placement` instead of silently dropping them.
+- `wdl tail` now recognizes control-initiated `session_idle` /
+  `session_expired` stream recycling and reconnects without presenting it as an
+  unknown warning.
+- `wdl doctor --strict` now exits non-zero when any local or remote readiness
+  check fails, while the default `wdl doctor` remains report-only.
+- `wdl r2` preserves empty object-key path segments while still rejecting `.`
+  and `..` segments, validates list `--limit` locally, and requires `--out`
+  when `objects get` would otherwise write raw bytes to an interactive terminal.
+- `wdl workflows status --step-limit` now requires `--include-steps`, matching
+  the control request it affects.
+- Top-level help for successful requests now prints to stdout, and
+  `wdl help <command>` prints that command's help.
+- When multiple Wrangler config files exist, deploy and D1 migrations now warn
+  which file is selected by Wrangler priority and which lower-priority files are
+  ignored; `wdl doctor` reports the same detail.
+
+### Fixed
+
+- Control connection failures, invalid 2xx JSON responses, unreadable
+  `wdl d1 execute --file` inputs, and unexpected positional arguments now fail
+  with CLI errors instead of raw Node errors or silently ignored input.
+- `wdl d1 migrations apply` now rejects symlinked `.sql` migration files instead
+  of silently dropping them.
+- `wdl deploy` now renders deploy warnings attached to failed upload responses,
+  including missing caller-secret hints, before reporting the control error.
+- Invalid `.assetsignore` patterns now report the offending pattern instead of
+  a bare `RegExp` error.
+- Project `.env` files with non-WDL dotenv extensions no longer break every WDL
+  command; the four WDL-consumed keys remain strictly parsed.
+- `wdl secret put/delete` no longer reports obsolete deferred-promote warnings;
+  current worker-secret mutations either promote atomically or return a retryable
+  control error.
+- Secret mutation failures now add command-specific guidance for env-budget,
+  contention, and secret-envelope errors, including that the failed mutation was
+  not written.
+- `wdl token list` now escapes credential labels and endpoints before rendering
+  the human table output.
+
+### Security
+
+- `wdl token` credential writes now use a temp-file plus rename so an existing
+  credentials symlink is replaced rather than followed.
+- `wdl token set/use/rm` now serialize credential-store read-modify-write
+  mutations with a recoverable lock, and credential-store temporary filenames
+  are unguessable.
+- Credential-store read and write failures now escape filesystem details before
+  rendering CLI errors.
+- `wdl tail` now caps SSE line buffering to avoid unbounded memory growth on a
+  malformed stream.
+- `wdl deploy` now registers process-exit and SIGINT/SIGTERM cleanup for its
+  temporary Wrangler config file.
+
+### Tests
+
+- Live CLI integration now exercises assets, Durable Objects, queues, cron
+  registration, and `wdl deploy --env` in addition to the existing command
+  surface.
+
 ## 1.3.1
 
 ### Fixed