Update development dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@headsdown/sdk	^0.2.14 → ^0.11.0
@types/node (source)	25.6.0 → 25.9.3
esbuild	0.28.0 → 0.28.1
vitest (source)	4.1.5 → 4.1.8

---

Release Notes

headsdownapp/headsdown-sdk (@​headsdown/sdk)

v0.11.0

Compare Source

Added

• Added HeadsDownClient.requestSessionTimeboxExtension() for requesting more time on an active session timebox using only an opaque session id and requested minute count.
• Added SessionTimeboxExtensionRequestInput, SessionTimeboxExtensionRequest, and SessionTimeboxExtensionRequestResult types for session timebox extension requests.
• Added optional session_ended.reason and session_ended.ended_at metadata to the IntegrationEvent vocabulary.

Changed

• Tightened TurnFailedReason and ToolFailedReason to closed manifest enums so TypeScript callers match hosted validation.

v0.10.0

Compare Source

Added

• Added the IntegrationEvent vocabulary: a vendor-neutral discriminated union covering session lifecycle (session_started, session_ended), turn lifecycle (turn_started, turn_ended, turn_failed), tool lifecycle (tool_invoked, tool_succeeded, tool_failed), authorization (permission_denied), and context (context_compacted).
• Added per-variant constructor helpers (sessionStartedEvent, turnFailedEvent, etc.) and a generic integrationEvent(context, event) that route through assertIntegrationEvent for eager shape, enum, opaque-id, and privacy validation.
• Added INTEGRATION_EVENT_TYPE namespace constants mapping each variant to its wire-level event type (integration.session_started, etc.). Wire events ride on the existing reportAgentRunEvent GraphQL mutation; no new transport is needed.
• Added INTEGRATION_EVENT_MANIFEST as the single source of truth for variant names, wire types, required and optional payload fields, and per-field enum value sets. Type aliases (SessionOutcome, TurnFailedReason, etc.) and runtime validation Sets are now derived from the manifest, so adding a variant or enum value is a single-edit change.
• Added schemas/integration-event-manifest.json, emitted from INTEGRATION_EVENT_MANIFEST by the new emit:integration-event-manifest npm script. Hosted backends (and any other language target) can read this JSON to assert their own validators stay in parity with the SDK.
• Added BucketLabel nominal alias documenting fields whose values are privacy-safe categorical labels (the runtime regex enforces the constraint).
• Added open-string-union escape hatches ((string & {})) on TurnFailedReason and ToolFailedReason, matching the existing AgentRunEventType pattern so future integrations can report new categories without an SDK upgrade.

Changed

• Extended the SDK privacy filter PROHIBITED_KEYS set with model_responses, transcript, transcripts, repo_name, git_repo, git_repository, git_branch, and source, aligning with the hosted prohibited-key list.
• Added an envelope-level top-level exemption to privacySafeClone so SDK-controlled envelope fields like source: "sdk" continue to flow through while the same key nested inside a payload is still rejected.
• Split the privacy walker into a validate-only path (validatePrivacySafe, no allocation) and the existing clone path (privacySafeClone, with allocation). assertPrivacySafe now uses the validate-only path, so eager validation in helpers no longer allocates a clone that gets discarded.

v0.9.0

Compare Source

Added

• Added the @headsdown/sdk/referee subpath with shared local Referee contract parsing, evidence normalization, evaluation, structured and markdown receipt rendering, outcome payload shaping, preview text, share-decision helpers, and recursive privacy filtering.
• Added submitLocalRefereeOutcomeSummary for privacy-filtered hosted outcome submission with a typed endpoint-unavailable result when the endpoint is unavailable.
• Added parameterized Local Referee client metadata so integrations can report privacy-safe client kind and version metadata without changing the outcome schema.
• Added an additive classifier telemetry manifest with SDK-owned vocabularies, a conversion helper for existing classifier results, and documentation for consumers that can keep using the SDK 0.6.0 minimal classifier subset until they adopt the richer manifest.
• Added shared deferred-decision re-attempt outcome helpers: DeferredDecisionReAttemptOutcome, DeferredDecisionReAttemptedPayload, deferredDecisionReAttemptedEvent, and client.reportDeferredDecisionReAttempted().

Fixed

• Updated the ask-user classifier fixture to use the canonical recovery_decision category.

v0.8.0

Compare Source

Added

• Added first-class SDK helpers for temporary availability overrides: getActiveAvailabilityOverride, createAvailabilityOverride, and cancelAvailabilityOverride.

v0.7.0

Compare Source

Added

• Added the @headsdown/sdk/agent subpath for pure agent adapter helpers, including shared HeadsDown call/action rendering and privacy-safe event builder exports.
• Added fetchAutopilotPolicy, AUTOPILOT_POLICY_QUERY, assertAutopilotPolicy, and AutopilotPolicyResponse for typed per-mode autopilot policy reads.

Fixed

• Tightened metadata-only agent event validation and context-aware enum handling for agent run event helpers.

v0.6.0

Compare Source

Added

• Added interaction.ask_user variant to ActionShape discriminated union with required question_category and recent_tool_context fields.
• Added exported types QuestionCategory and RecentToolContext for the new variant.
• Added isInteractionAskUserActionShape type guard.
• Extended classifyActionShapeFallback with deterministic classification for interaction.ask_user: baseline notable, reclassified to permanent on recovery_decision + failed, reclassified to routine on tooling_choice + succeeded.
• Extended buildClassifierPromptFragments with ask_user fixture references in taxonomyFragment and ask_user guidance in instructionsFragment.
• Added four representative CLASSIFIER_FIXTURES entries for the new variant.
• Bumped AUTOPILOT_CLASSIFIER_VERSION from 1.0.0 to 1.1.0. Old SDKs pinned to 1.0.0 degrade safely via the existing unknown-variant fallback.
• Added tests: type-level discrimination, all four fixture cases, malformed-shape fail-closed coverage, valid-combination property coverage (no valid combination produces trivial/critical/classification_failed), and 1.0.0 ↔ 1.1.0 version-compatibility regression.
• Updated README with interaction.ask_user usage, deterministic rules table, and action-schema extension guide.

v0.5.1

Compare Source

Added

• Added deferred_decision.resolved agent-run SDK support:
  • DeferredDecisionResolutionKind, DeferredDecisionNotesBucket, and DeferredDecisionResolvedPayload types.
  • deferredDecisionResolvedEvent(context, payload) builder with deterministic idempotency key format {run_id}:deferred_decision.resolved:{decision_id}.
  • client.reportDeferredDecisionResolved(context, payload) helper.
• Added client.listAgentRunEvents(args) and LIST_AGENT_RUN_EVENTS_QUERY for reading event streams with optional resolutionKind filtering.
• Added tests for resolved-event builder/client round-trip and listAgentRunEvents query variable wiring.

v0.5.0

Compare Source

Added

• Added a shared autopilot classifier substrate export surface:
  • severity taxonomy definitions and fixtures
  • policy-aware classifier prompt fragments
  • typed action-shape schema with conservative unknown-variant fallback
  • pure escalation decision logic with capability-aware sandbox handling
• Added classifier version compatibility helpers for major/minor mismatch handling semantics.
• Added classifier substrate tests for fixtures, escalation path properties, unknown variant fallback, capability-aware behavior, and version mismatch handling.
• Added a shared LocalSessionSummary SDK contract with strict TypeScript typing, schema export constants, and assertLocalSessionSummary() validation.
• Added a published JSON schema artifact at schemas/local-session-summary.schema.json for non-TypeScript consumers and validator pipelines.

Changed

• Expanded README with classifier substrate usage, extension expectations, read-fresh policy contract, and version-mismatch behavior.

LocalSessionSummary guidance

Include only derived session facts:

• Version and generated timestamp metadata.
• Opaque session/proposal references.
• Boolean state flags (stale, continuation artifact availability, local validation outcome).
• Numeric counters (tool calls, file changes, deferred decisions).
• Outcome category (in_progress, completed, tabled, deferred_for_review).

Do not include raw context:

• Prompts, model outputs, or transcripts.
• File paths, repo names, branch names, or diffs.
• Logs, stack traces, URLs, or secrets.

Example:

const summary: LocalSessionSummary = {
  version: 1,
  sessionId: "session_123",
  generatedAt: new Date().toISOString(),
  stale: false,
  toolCallCount: 8,
  fileChangeCount: 3,
  deferredDecisionCount: 1,
  continuationArtifactAvailable: true,
  validationLocallyPassed: true,
  approvedProposalRef: "proposal_456",
  outcomeCategory: "completed",
};

v0.4.0

Compare Source

Added

• Added SDK type support for the attention_window_closing HeadsDown call key, covering the attended-mode window-closing rescue flow.

Changed

• Refreshed generated schema types for finish_line_friction. The server now recommends narrow_scope for this call via the recommended_action_key field, replacing the previous pause_and_summarize recommendation. SDK consumers should read the server-provided value and avoid hardcoding the old default.

Note

• rabbit_hole_detected remains in the type union and is still valid for compatibility. Do not introduce new uses of it. Clients implementing the new contract must not render it as a hard-stop; treat it like keep_it_tight if encountered.

v0.3.1

Compare Source

• Added SDK type support for the finish_line_friction HeadsDown call key.

v0.3.0

Compare Source

• Added privacy-safe agent run event reporting helpers for canonical HeadsDown event taxonomy.
• Added reportAgentRunEvent() and named helpers for run lifecycle, progress, scope drift, continuation, queue, resume, terminal, and steering outcome events.
• Added structured progressPayload GraphQL serialization, metadata-only privacy validation, bucket helpers, and generated schema/types for the #​906 backend event ingestion API.

v0.2.15

Compare Source

• Added SDK helpers for applying canonical HeadsDown actions, including queueing, pausing, resuming, narrowing, stopping, and temporary exception flows.
• Added typed action errors for invalid state, expired action, feature disabled, and auth failure.
• Added idempotency key derivation for HeadsDown action helpers and typed GraphQL operation coverage for applyHeadsdownAction.

evanw/esbuild (esbuild)

v0.28.1

Compare Source

• Disallow \\ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \\ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \\ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#​4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  
  // Old output (with --minify)
  new Resource().activate();
  
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#​4461, #​4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#​4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  
  // Old output
  new foo()`bar`();
  new (foo())?.bar();
  
  // New output
  new (foo())`bar`();
  new (foo()?.bar)();

• Fix renaming of nested var declarations (#​4471)

  This release fixes a bug where var declarations in nested scopes that are hoisted up to module scope were not correctly being renamed during bundling. That could previously lead to name collisions when minification was disabled, which could potentially cause a behavior change. The bug has been fixed so that these hoisted declarations are now considered to be module-level symbols during the name collision avoidance pass.

• Emit var instead of const for certain TypeScript-only constructs for ES5 (#​4448)

  While esbuild doesn't generally support converting const to var for ES5 due to nested scoping rules (which is currently a build-time error), esbuild previously incorrectly converted TypeScript-only import assignment constructs into a const declaration even when targeting ES5. With this release, esbuild will now use var for this case instead:

  // Original code
  import x = require('y')
  
  // Old output (with --target=es5)
  const x = require("y");
  
  // New output (with --target=es5)
  var x = require("y");

vitest-dev/vitest (vitest)

v4.1.8

Compare Source

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in #​10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple ids [backport to v4]  -  by @​toxik and @​Zelys-DFKH in #​10474 (675b4)

    View changes on GitHub

v4.1.7

Compare Source

   🐞 Bug Fixes

• runner: Limit concurrency per task branch in addition to per leaf callbacks (backport)  -  by @​hi-ogawa in #​10384 (4f0f2)

    View changes on GitHub

v4.1.6

Compare Source

   🐞 Bug Fixes

• browser: Provide project reference in ToMatchScreenshotResolvePath  -  by @​macarie and @​sheremet-va in #​10138 (31882)
• Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options  -  by @​hi-ogawa, Codex and @​sheremet-va in #​10196 (2847d)
• browser: Simplify orchestrator otel carrier  -  by @​hi-ogawa in #​10285 (18af9)

   🏎 Performance

• Stringify diff objects only once  -  by @​sheremet-va in #​10276 (9f7b1)

    View changes on GitHub

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • "before 5am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.