v0.2.1 — Fix subcommand dispatch under fledge install

Fix

fledge github <checks|issues|prs> failed with No such file or directory after installing v0.2.0 via fledge plugins install.

Root cause

fledge plugins install symlinks only the declared binary (bin/fledge-github) into its shared plugin bin dir. Helper scripts (fledge-github-{checks,issues,prs}) live one directory up in the cloned plugin source. The v0.2.0 dispatcher used dirname "$0" to find siblings — which resolved to the shared bin (no helpers there), not the real plugin source.

Fix

Walk the symlink chain via the standard BASH_SOURCE + readlink idiom to recover the real plugin directory before looking up subcommand helpers.

Upgrade

fledge plugins update

If you installed v0.2.0 and saw the dispatch error, this release fixes it.

v0.2.0 — Nest commands under `fledge github`

Breaking change

All commands are now nested under a single github command. This collapses the previously-flat surface and leaves the top-level namespace clean for non-GitHub forges.

Migration

Before	After
fledge checks	fledge github checks
fledge issues	fledge github issues
fledge prs	fledge github prs

All flags, output formats, and JSON shapes are unchanged — only the invocation path moved.

Why

The flat surface baked "all dev happens on GitHub" into fledge's command namespace. Nesting under fledge github keeps the top level honest for users on GitLab/Gitea/self-hosted Git, and makes room for a future fledge-plugin-gitlab to register fledge gitlab ... alongside without colliding.

Internals

• bin/fledge-github is a thin dispatcher
• Each subcommand remains a self-contained POSIX-ish shell script (bin/fledge-github-{checks,issues,prs})