chore(flake): bump construct for orca-cli revision 37

[UnbreakableMJ]

Picks up Construct 3a74842, which returns the vendored orca-cli skill to Orca release revision 37.

Why

Revision 36 was pinned deliberately on 2026-08-19: revision 37 advertised share skills while the installed Orca's orca skills offered only list, get, install and update — the skill described a command the binary did not have.

The Orca AppImage has since been rebuilt (2026-08-22). Its manifest now lists orca-cli at revision 37, and:

$ orca skills --help
  share    Publish explicitly selected installed skills behind one unlisted link

So 36 became the copy that was wrong about the tool. The pin was a hold, not a destination.

Scope — larger than the title suggests

Only the construct input moves, but it moves from a46c108 (2026-08-18), not from 8b20eee. So it crosses Construct #46 and #47 as well as the orca-cli fix.

That is what the second commit is about. skills-drift correctly failed the first push: .github/skills/ is a vendored real-file copy of the pinned tree (the Copilot coding agent, Copilot CLI and VS Code agent modes get a plain git clone and cannot follow a symlink into the Nix store), so a pin bump without a re-sync leaves it stale. pkgs/sync-skills.nu documents the re-run as the required second step.

The regenerated content is almost entirely the §4.3 license-file rename from #46/#47 — LICENSE-GPL/LICENSE-MIT → LICENSE.GPL/LICENSE.MIT, a per-skill LICENSE added to every bundle, duplicated LICENSE.md bodies dropped — plus the v1.50 spacecraft-steelbore-standard text. None of it is the Orca change: this vendored subset is 13 Copilot-facing skills and the three Orca leaves are not among them.

nu pkgs/sync-skills.nu --check now reports .github/skills matches Construct 3a74842e.

nixpkgs-unstable, home-manager-unstable and antigravity-nix are deliberately left alone. An unrelated four-input nix flake update was sitting uncommitted on feat/multimedia-exiftool-imagemagick when this was branched; that work is untouched and still there.

Verification

The pinned revision builds the intended tree — each vendored Orca skill hash-matches the installed app's resources/skills/current-manifest.json:

computer-use     rev 8   MATCH
orca-cli         rev 37  MATCH
orchestration    rev 28  MATCH

What this does not do

It does not silence Orca's "Skipped" dialog, and is not meant to. The three skills install into ~/.agents/skills, a symlink into /nix/store — a read-only path Orca never wrote to and cannot write to. It skips what it does not own regardless of content, which is why two skills already byte-identical to its own manifest were flagged too. Rationale, and why the dialog's "remove it" advice must not be followed, are in orca-skills/CREDITS.md.

Applying this needs sudo nixos-rebuild switch (home-manager is an integrated NixOS module here), which is left to the maintainer.

🤖 Generated with Claude Code

https://claude.ai/code/session_017hj64PwFDDJsNdAJoEuYpB

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 12dd15a572

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Sign the dependency bump commit

For the reviewed commit c5d2f2f4483fddc5fcb32bc145a8c49e3f793fff, the commit object has no gpgsig header and git verify-commit exits with status 1, so this dependency bump does not satisfy the repository's mandatory Signed & Verified policy. Recreate the commit with the configured Ed25519 SSH signing key before merging.

AGENTS.md reference: AGENTS.md:L348-L348

Useful? React with 👍 / 👎.