repobuddy@1.6.0

Minor Changes

• 2bcf2a0: Bump clibuilder from ^10.1.0 to ^11.0.0. The prior ^10.1.0 range could never
  cross into the published 11.0.0 major (a caret cannot span majors), which meant every
  consumer of @repobuddy/typescript — roughly 46 repos in the estate use it as a
  devDependency — kept resolving clibuilder@10.1.0 and, through it, a stale type-plus
  and tersify major in their tree even after those packages published current majors.

  clibuilder@11.0.0's own major came from a type-plus@8 pin (its emitted .d.ts now
  requires TypeScript >= 5.6.0), not from an API change — the PluginActivationContext
  shape @repobuddy/typescript re-exports is unchanged, so this is not a breaking change
  for consumers on TypeScript >= 5.6 (this repo already requires ^7.0.0/^6.0.0).
  Shipping it as minor here lets the ~46 consumers of @repobuddy/typescript pick up
  the fix and drop the stale transitive type-plus/tersify majors without a forced
  major bump of their own.

• ed7323a: Add the llms-txt skill.

  llms.txt is the orientation file an agent reads before using a package or site: what the project
  is, the conventions that govern its whole surface, and where the per-item detail lives. The skill
  generates it from the project's real public surface rather than hand-writing it — a hand-written one
  rots into describing an API that was removed two releases ago — wires a drift check into the command
  CI already runs, and reports the documentation gap that generating from the real surface exposes
  instead of trying to fill it in the same change.

  It also draws the audience boundary against AGENTS.md: llms.txt addresses whoever consumes the
  published thing, AGENTS.md whoever changes the repo. A project with no public surface needs only
  the second, and the skill says so rather than generating a file with no reader.

repobuddy@1.5.2

Patch Changes

• e3026f9: Bump clibuilder to the latest published ^10.1.0 (in-range, non-breaking) picked up
  while sweeping type-plus across the estate. No source change needed.

• d967c8a: to-question: sort dialect references by family instead of by platform name.

  assets/github.md, assets/gitlab.md and assets/asana.md are folded into assets/markdown.md,
  which now carries the Markdown baseline, a per-platform capability table (headings, tables, task
  lists, strikethrough, alerts, code blocks) and short platform notes for the quirks that change what
  gets written. assets/ holds one file per dialect family — Markdown, Slack mrkdwn, Jira wiki
  markup, and email — so a new Markdown-family platform costs a row rather than another near-duplicate
  file. A platform the skill has no row for falls back to the Markdown baseline and says so.

• 25da932: to-question: derive the handoff file path instead of hardcoding /tmp/question.md.

  The new bundled scripts/question-path.mjs resolves the OS temp directory (honoring TMPDIR/TEMP,
  so it is correct on Linux, macOS, WSL and native Windows) and mints a fresh private mkdtemp
  directory per session. Two users or two concurrent sessions on a shared machine can no longer collide
  on the same world-readable filename.

@repobuddy/vitest@2.2.0

Minor Changes

• 9492362: Recognise ts/ as a source directory.

  The include globs covered {src,source,code} while @repobuddy/jest has always
  resolved ['src', 'source', 'ts', 'js']. Most of these repos keep their sources in
  ts/, so the vitest presets matched nothing and every migration so far
  (resolve.imports, path-equal, just-func, fsa-emitter) hand-wrote a
  vitest.config.ts rather than importing the preset.

  js is deliberately not added. @repobuddy/jest picks the first existing
  directory from its list, whereas these are globs that union everything they match —
  so adding js risks pulling a build-output directory into the source set. No repo
  uses js/ as a source directory today.

@repobuddy/typescript@2.2.0

Minor Changes

• 2bcf2a0: Bump clibuilder from ^10.1.0 to ^11.0.0. The prior ^10.1.0 range could never
  cross into the published 11.0.0 major (a caret cannot span majors), which meant every
  consumer of @repobuddy/typescript — roughly 46 repos in the estate use it as a
  devDependency — kept resolving clibuilder@10.1.0 and, through it, a stale type-plus
  and tersify major in their tree even after those packages published current majors.

  clibuilder@11.0.0's own major came from a type-plus@8 pin (its emitted .d.ts now
  requires TypeScript >= 5.6.0), not from an API change — the PluginActivationContext
  shape @repobuddy/typescript re-exports is unchanged, so this is not a breaking change
  for consumers on TypeScript >= 5.6 (this repo already requires ^7.0.0/^6.0.0).
  Shipping it as minor here lets the ~46 consumers of @repobuddy/typescript pick up
  the fix and drop the stale transitive type-plus/tersify majors without a forced
  major bump of their own.

@repobuddy/typescript@2.1.3

Patch Changes

• e3026f9: Bump clibuilder to the latest published ^10.1.0 (in-range, non-breaking) picked up
  while sweeping type-plus across the estate. No source change needed.

@repobuddy/jest@7.0.0

Major Changes

• 2748090: Use jest-watch-toggle-config instead of the jest-watch-toggle-config-2 fork.

  The fork existed because the original looked unmaintained — specifically it carried a
  pointless jest-validate peer dependency, raised as jest-community/jest-watch-toggle-config#19.
  Upstream 3.0.0 (April 2023) dropped that peer and closed the issue, and it has been
  "type": "module" since the same release. Verified against a real jest 30.5.1 install:
  the original loads, constructs, and toggles correctly with no flags.

  Breaking: knownWatchPlugins.toggleConfig() now emits 'jest-watch-toggle-config'.
  The optional peer changed name accordingly. If you use defineWatchPlugins() or
  toggleConfig(), swap the devDependency:

  pnpm remove jest-watch-toggle-config-2
  pnpm add -D jest-watch-toggle-config
  

  Consumers who never enabled the toggle-config plugin are unaffected.

@repobuddy/jest@6.0.0

Major Changes

• 10720a2: Pin type-plus to the exact 8.0.0-beta.10, part of an estate-wide sweep off type-plus 7.

  AnyRecord appears in this package's emitted declarations (src/fields/transform.ts), so
  consumers resolve type-plus's own .d.ts and inherit its new typescript >= 5.6.0 peer
  dependency — type-plus 5, 6 and 7 declared no typescript peer at all. Hence major.

  NonUndefined was removed in type-plus 8; src/fields/transform.ts and
  src/fields/watchPlugins.ts now use Exclude<T, undefined>, the direct equivalent.

  Pinned rather than caret-ranged: ^8.0.0-beta.10 would also admit every later 8.0.0
  prerelease plus 8.0.0 and 8.1.0, and this is a prerelease line where breaking changes
  land between betas (beta.10 -> beta.11 changed Equal's signature and removed isType.f).
  An exact version makes each bump a reviewable PR rather than something a lockfile refresh
  can do silently.

@repobuddy/jest@5.0.2

Patch Changes

• 59773cc: Remove the broken config.mjs file from the published package.

  config.mjs contained export * from './esm/config.js', but no src/config.ts
  exists and so esm/config.js was never emitted. The file shipped in every
  release through the files list and was not reachable through exports, so
  importing @repobuddy/jest/config.mjs threw ERR_MODULE_NOT_FOUND. Verified
  against the published 5.0.1 tarball.

  Nothing that works today can break: the only thing the file could do was throw.

@repobuddy/biome@2.4.0

Minor Changes

• 4641fd7: Raise useNodejsImportProtocol to error in both recommended and performant.

  Biome ships this rule at info, which prints the finding and still exits 0. It
  therefore read as enforced in any config review while gating nothing — a
  fleet-wide audit found it reporting and passing on every repo extending this
  preset. Both presets already promote nine other Biome-2 style rules from info
  to error; this one was simply missing from that list.

  Verified by exit code rather than by reading config. On a file containing
  import { deepEqual } from 'assert':

  before: exit 0 — "Found 1 info."
  after:  exit 1 — "Some errors were emitted while running checks."
  

  The node: prefix is what distinguishes a Node builtin from a same-named package
  on the registry, so this is a supply-chain signal and not only a style preference.

  This can newly fail check in consuming repos. The violation is auto-fixable:
  biome check --write rewrites 'fs' to 'node:fs'. Run it when taking this
  version.

@repobuddy/typescript@2.1.2

Patch Changes

• 5789ca2: Build with TypeScript 7.

  The emitted output changes cosmetically: TypeScript 7 preserves the source
  quote style in re-export specifiers (export * from './x.js' rather than
  "./x.js"), and the property order inside one inferred .d.ts union in
  @repobuddy/typescript differs. No public API, type or runtime behavior
  changes.

  The tsconfig presets themselves are unchanged and remain valid under both
  TypeScript 6 and 7 — they use no option TypeScript 7 removed, and
  @repobuddy/typescript now type-checks and builds against 7.0.2 using them.