fix(josh-sync): expose yq directly in the consumer devenv module

devenvModules.default only added the wrapProgram-wrapped josh-sync binary,
whose bundled PATH (yq, jq, etc.) only applies while josh-sync itself runs.
Plain `yq` was never actually on PATH in a consumer's devenv shell, breaking
the manual `yq -i` config-editing commands the josh-sync skill's docs call
for. Adds pkgs.yq-go to the module's packages list directly. Bumps to v2.3.1.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TNXgcFWVgSh3wkQS55cCX6

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 2.3.1
+
+### Fixes
+
+- **`devenvModules.default` now exposes `yq` directly.** The `josh-sync` package it includes is `wrapProgram`-wrapped, so its bundled PATH (yq, jq, etc.) only applied while `josh-sync` itself was running — plain `yq` was never actually on PATH in a consumer's devenv shell. This broke the manual `yq -i` config-editing commands the josh-sync skill's docs call for (e.g. schema migrations) on any project without a system-wide yq install. `pkgs.yq-go` is now added to the module's `packages` list directly.
+
 ## 2.3.0
 
 ### Features

VERSION

@@ -1 +1 @@
-2.3.0
+2.3.1

flake.nix

@@ -57,8 +57,15 @@
         });
 
       # devenv module for consumers
+      #
+      # `self.packages.${pkgs.system}.default` is wrapProgram-wrapped, so its
+      # PATH additions (yq, jq, etc.) only apply while `josh-sync` itself is
+      # running — they don't reach the ambient devenv shell. Add yq-go
+      # directly so consumers can run the `yq -i` commands the josh-sync
+      # skill's config-editing docs call for (e.g. schema migrations),
+      # without needing a system-wide yq install.
       devenvModules.default = { pkgs, ... }: {
-        packages = [ self.packages.${pkgs.system}.default ];
+        packages = [ self.packages.${pkgs.system}.default pkgs.yq-go ];
         dotenv.disableHint = true;
       };