Compile Sessionizer plugin entrypoints into executables

[andrewchng]

What to build

Replace the Sessionizer plugin's Bun runtime entrypoints with compiled executables so Herdr actions and panes can launch the plugin without depending on bun run at runtime.

This slice should cover the end-to-end path: produce executable artifacts for the plugin entrypoints, point the plugin manifest at those artifacts, and verify that the Sessionizer and Worktree flows still open and run correctly through Herdr.

Acceptance criteria

• Plugin action and pane entrypoints run from compiled executables instead of bun run.
• Sessionizer and Worktree flows still work through the plugin manifest with the compiled artifacts.
• The runtime path no longer requires Bun to be present just to launch the already-built plugin entrypoints.

Blocked by

None - can start immediately

[andrewchng]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Compile the four plugin-manifest entrypoints into host-local executables and launch them without bun run at runtime.

Current behavior:

• Plugin actions and panes are declared with bun run against TypeScript sources.
• The plugin [[build]] step only installs dependencies; it does not produce executables.
• README treats Bun as both build and runtime dependency.
• Local plugin link and GitHub CI do not compile plugin entrypoints.
• Optional CLI bin for worktree remains Bun-driven and is unrelated to the plugin-manifest path.

Desired behavior:

• After install/build (or an explicit package build script for link/dev), four host-local standalone executables exist:
  • dist/open — action open
  • dist/worktree-open — action worktree-open
  • dist/sessionizer — pane sessionizer
  • dist/worktree — pane worktree
• The plugin manifest action/pane command entries invoke those executables (relative to plugin root), not bun run on sources.
• [[build]] runs frozen lockfile install, then the same compile recipe that the package build script uses.
• Compile is host-only (bun build --compile on the machine running build). No multi-arch matrix or prebuilt download in this issue.
• README distinguishes: Bun still required for install/build (and maintainer workflows); Bun is not required merely to launch already-built actions/panes. Do not claim zero-Bun install.
• CI runs the package build and fails if any of the four dist/* artifacts is missing or not executable.
• Sessionizer and Worktree product behavior (pickers, focus/create, layout bootstrap rules) is unchanged; only how the plugin is launched changes.

Key interfaces:

• herdr-plugin.toml — [[actions]] / [[panes]] commands point at dist/* executables; [[build]] produces them after install.
• Package scripts — a build script that compiles the four entrypoints into the names above (shared with [[build]]).
• Compile inputs — existing action openers and pane runners for Sessionizer and Worktree (sources remain the compile inputs; structure may move but roles must be preserved).
• CI workflow — after install/typecheck/tests (or equivalent), run build and assert the four artifacts.
• Gitignore — compiled dist/ output should not be committed.

Acceptance criteria:

• bun run build (or the chosen package script name) produces four executables at dist/open, dist/worktree-open, dist/sessionizer, and dist/worktree.
• Plugin manifest action/pane commands reference those executables and do not use bun run for those four surfaces.
• [[build]] installs with frozen lockfile then runs the same compile recipe (so herdr plugin install builds host binaries).
• Package build is documented for local plugin link / iteration (link does not replace a full install build).
• Existing unit/typecheck suite still passes; CI also runs build and fails if any of the four artifacts is missing/non-executable.
• Manual smoke: after build + link (or reinstall), sessionizer.open and sessionizer.worktree-open open their pickers and complete a normal happy path without needing Bun on PATH for the launch itself.
• README requirements/setup state Bun is still needed for install/build, and that launch uses compiled artifacts (no overclaim of zero-Bun install).
• dist/ is gitignored.

Out of scope:

• Prebuilt release assets, download-on-install, checksum verification, multi-arch matrices (issue Decide and document Sessionizer binary distribution model #4 — product end goal of zero Bun for end users at install).
• Compiling or changing the optional herdr-worktree CLI / package bin.
• Linux platform enablement or expanding platforms beyond current macOS declaration (Validate Linux support and re-enable platforms in manifest #6).
• Changing Sessionizer/Worktree UX, config schema, layout bootstrap rules, or picker behavior.
• Claiming or implementing install without Bun.

Related:

• Product end goal (later): zero Bun for end users at install and launch — Decide and document Sessionizer binary distribution model #4 after this lands.
• Decide and document Sessionizer binary distribution model #4 remains the distribution decision/implementation; this issue only makes the runtime path executable-based.

[andrewchng]

This was generated by AI during triage.

Agent Brief (revised)

Category: enhancement
Summary: Compile plugin launch into a single host-local executable that supports both Sessionizer and Worktree (and their action launchers), and point the manifest at that one binary with different argv modes.

Supersedes: the earlier agent brief on this issue that specified four separate dist/* binaries. Use this brief.

Product / architecture context

Herdr distinguishes actions (keybind / plugin action invoke surface) from panes (placed UI processes). Sessionizer uses two pairs:

1. Sessionizer: action open → herdr plugin pane open --entrypoint sessionizer → pane sessionizer runs the real picker (runSessionizer).
2. Worktree: action worktree-open → pane open --entrypoint worktree → pane worktree runs the worktree flow (runWorktree).

Action and pane are not the same code path: actions are short launchers; panes are the fzf/UX bodies. Packaging still ships one binary that implements all four modes via argv.

Current behavior:

• Four separate bun run <source> commands in the plugin manifest (two actions, two panes).
• [[build]] only runs dependency install; no compile step.
• README treats Bun as build and runtime.
• CI does not compile plugin entrypoints.
• Optional package bin for scripted worktree remains Bun-driven and is out of scope.

Desired behavior:

• One host-local standalone executable, e.g. dist/sessionizer (exact filename may match package/plugin naming; keep it stable and documented).
• That binary accepts modes for all four manifest roles, for example:
  • open — action launcher: open pane entrypoint sessionizer (placement/focus/target behavior preserved)
  • sessionizer — pane body: Sessionizer flow
  • worktree-open — action launcher: open pane entrypoint worktree (env passthrough for project/branch/command preserved)
  • worktree — pane body: Worktree flow
• Manifest shape (illustrative):

[[actions]]
id = "open"
command = ["./dist/sessionizer", "open"]

[[actions]]
id = "worktree-open"
command = ["./dist/sessionizer", "worktree-open"]

[[panes]]
id = "sessionizer"
command = ["./dist/sessionizer", "sessionizer"]

[[panes]]
id = "worktree"
command = ["./dist/sessionizer", "worktree"]

• [[build]] runs frozen lockfile install, then the same compile recipe as the package build script (single bun build --compile producing that one artifact).
• Compile is host-only. No multi-arch prebuilts or download-on-install in this issue.
• README: Bun still required for install/build (and maintainer workflows); Bun is not required merely to launch already-built actions/panes. Do not claim zero-Bun install (Decide and document Sessionizer binary distribution model #4).
• CI runs package build and fails if the single artifact is missing or not executable.
• Sessionizer/Worktree product behavior unchanged; only packaging and how the process is started.

Key interfaces:

• Plugin manifest — all four action/pane commands invoke the same relative executable with different mode args; no bun run for those surfaces.
• Package build script — shared with [[build]]; produces one host executable under dist/.
• CLI dispatcher — single entry that routes argv modes to existing launcher vs flow behavior (preserve open-pane placement rules and worktree env→argv bridging).
• CI — after install/tests, run build and assert the one artifact.
• Gitignore — dist/ build output not committed.

Acceptance criteria:

• bun run build produces a single executable under dist/ (e.g. dist/sessionizer).
• Manifest action/pane commands all use that executable with distinct mode args; none of the four surfaces use bun run on TypeScript sources.
• Modes cover: open launcher, sessionizer pane body, worktree-open launcher, worktree pane body — with current placement/focus/env behavior preserved.
• [[build]] installs with frozen lockfile then runs the same compile recipe.
• Package build is documented for local plugin link / iteration.
• Unit/typecheck still pass; CI runs build and fails if the artifact is missing/non-executable.
• Manual smoke: after build + link (or reinstall), sessionizer.open and sessionizer.worktree-open open their pickers and complete a normal happy path without needing Bun on PATH for launch.
• README distinguishes Bun for install/build vs launch via compiled binary; no zero-Bun install claim.
• dist/ is gitignored.

Out of scope:

• Prebuilt release assets, fetch-on-install, multi-arch matrices (Decide and document Sessionizer binary distribution model #4 — end goal of zero Bun at install).
• Compiling or changing the optional herdr-worktree package bin (can share code later; not required here).
• Collapsing action+pane into a single Herdr concept or removing launchers (keep action → pane open design).
• Linux platform enablement / expanding platforms (Validate Linux support and re-enable platforms in manifest #6).
• Changing Sessionizer/Worktree UX, config schema, or layout bootstrap rules.

Related:

• Product end goal: zero Bun for end users at install and launch — Decide and document Sessionizer binary distribution model #4 after this.
• One binary is intentional for packaging size and future prebuilts; four modes remain because Herdr actions and panes are different invocation roles.

[andrewchng]

This was generated by AI during triage.

Agent Brief (revised — one binary packaging)

Category: enhancement
Summary: Ship a single host-local executable dist/sessionizer that implements both Sessionizer and Worktree (launchers + pane bodies), wire the plugin manifest to it with stable action/pane ids, and keep the update non-breaking for existing keybind users.

Supersedes: prior agent briefs on this issue (four binaries, and the earlier one-binary draft). Use this brief.

Architecture (Herdr vs binary)

• Herdr owns actions vs panes. Keybinds use plugin_action → sessionizer.open / sessionizer.worktree-open.
• Action modes open a Herdr pane (herdr plugin pane open --entrypoint …); they do not run fzf.
• Pane modes run the real flows (runSessionizer / runWorktree).
• Bun only builds the one binary; it does not define action vs pane.

Two pairs, one artifact:

1. open → pane open --entrypoint sessionizer → mode sessionizer (picker body)
2. worktree-open → pane open --entrypoint worktree → mode worktree (worktree body)

Public compatibility (non-breaking)

Do not change (users depend on these):

• Plugin id: sessionizer
• Action ids: open, worktree-open
• Pane ids: sessionizer, worktree

May change (packaging only):

• Manifest command arrays
• Build pipeline and dist/sessionizer

Changelog: packaging/runtime launch change, not a keybind migration.

Binary contract

Path: dist/sessionizer (single host-local bun build --compile artifact).

Invocation:

./dist/sessionizer <mode> [args...]

Mode	Role
open	Action launcher → Sessionizer pane
sessionizer	Pane body — Sessionizer flow
worktree-open	Action launcher → Worktree pane (preserve env passthrough for project/branch/command)
worktree	Pane body — Worktree flow

• First arg = mode (required unless help).
• Remaining args = forwarded into that mode’s implementation (power users + possible future Herdr arg passthrough). Do not globally reject extra args.
• No args / --help / -h: print short usage listing the four modes; exit 0.
• Unknown mode: print usage + error; exit non-zero.

Illustrative manifest:

[[actions]]
id = "open"
command = ["./dist/sessionizer", "open"]

[[actions]]
id = "worktree-open"
command = ["./dist/sessionizer", "worktree-open"]

[[panes]]
id = "sessionizer"
command = ["./dist/sessionizer", "sessionizer"]

[[panes]]
id = "worktree"
command = ["./dist/sessionizer", "worktree"]

(Herdr may pass additional argv later; forwarding keeps that viable. Local power use: ./dist/sessionizer worktree --project … etc. as the runners already support.)

Build / install / docs / CI

Current behavior:

• Four bun run <source> commands in the manifest.
• [[build]] only installs deps.
• README treats Bun as build and runtime.
• CI does not compile the plugin binary.

Desired behavior:

• [[build]]: frozen lockfile install, then the same compile recipe as package build, producing dist/sessionizer only (host-only compile).
• Package build script for plugin link / iteration (link does not replace install build).
• No bun run for the four plugin surfaces.
• README: Bun still required for install/build (and maintainers); Bun not required merely to launch already-built actions/panes. No zero-Bun install claim.
• CI: run build; fail if dist/sessionizer is missing or not executable.
• dist/ gitignored.
• Product UX (pickers, layout bootstrap rules) unchanged.

Key interfaces:

• Plugin manifest — stable ids; commands → ./dist/sessionizer + mode.
• Package build + [[build]] — one shared compile recipe → dist/sessionizer.
• CLI dispatcher — mode routing + arg forwarding + help/unknown-mode behavior above.
• Existing launcher placement/focus rules and worktree env→options bridging must keep working under the new modes.
• CI artifact check for the single binary.

Acceptance criteria:

• bun run build produces executable dist/sessionizer only (not four binaries).
• Manifest keeps action ids open / worktree-open and pane ids sessionizer / worktree; commands use ./dist/sessionizer with the matching mode; no bun run on those four surfaces.
• Dispatcher: open | sessionizer | worktree-open | worktree; forwards [args...] after mode; help on no-args/--help/-h (exit 0); unknown mode fails non-zero.
• Launchers still open the correct pane entrypoints with current placement/focus/env behavior; pane modes still run Sessionizer and Worktree flows.
• [[build]] = frozen install + same compile recipe; package build documented for link/dev.
• Unit/typecheck pass; CI runs build and fails without a usable dist/sessionizer.
• Manual smoke: after build + link (or reinstall), sessionizer.open and sessionizer.worktree-open work without Bun on PATH for launch; existing keybind strings still valid.
• README: Bun for install/build vs compiled launch; no zero-Bun install claim; dist/ gitignored.

Out of scope:

• Prebuilts / fetch-on-install / multi-arch (Decide and document Sessionizer binary distribution model #4).
• Renaming action or pane ids (breaking).
• Collapsing action+pane into one Herdr concept.
• Wiring package.json bin to dist/sessionizer (optional later; herdr-worktree stays separate).
• Linux platforms expansion (Validate Linux support and re-enable platforms in manifest #6).
• Sessionizer/Worktree UX, config schema, layout bootstrap changes.

Related:

• End goal: zero Bun for end users at install and launch → Decide and document Sessionizer binary distribution model #4 after this.
• One binary chosen for size and future prebuilts; four modes remain because Herdr actions and panes are different invocation roles.

[andrewchng]

Picked up in worktree issue-3-compile-sessionizer-plugin-entrypoints-into-execut.