Phaneslight

PhanesLight

⚠️ v3.7.1 — This repository is the MANUAL install again

**The plugin release that landed here at v3.7.0 was a mistake, and it is reverted.** The plugin was built for the **Claude community marketplace** and was never meant to replace this repository's contents. Publishing it here retired the manual install path as a side effect, which was not the intent. It has been moved to its own home at [`github.com/Aloim/phanesplugin`](https://github.com/Aloim/phanesplugin), and **this repository is the manual, single-file PhanesLight, as it was through v3.6.1.**

**If you are on the manual install (you fetched `phaneslight.md` into `.claude/commands/`), nothing was ever taken away from you.** v3.6.2 announced that your path was closing. Disregard it. Fetch v3.7.1 and carry on; see [Upgrading an older install](#upgrading-an-older-install).

**If you installed the plugin from this repository in the meantime**, the marketplace here no longer resolves. Either re-add it from `Aloim/phanesplugin`, or move to the manual install; both routes are written out under [Coming from the plugin](#coming-from-the-plugin).

**There is no manual v3.7.0**, because v3.7.0 was the plugin. A manual install goes from v3.6.1 straight to v3.7.1.

**Two rules changed in the lineup.** The haiku tier, `-mechanic`, no longer writes code of any kind, and escalates from LOW upward because it can no longer absorb even a trivial fix itself. And `-reviewer` now reviews your plan before the run starts, and may write plan files; the old flat claim that it "never writes" was always contradicted by its own job and is corrected to "never writes code".

**v3.7.1 is published to BOTH `Aloim/phaneslight` and the legacy `Aloim/phanes`,** as v3.6.1 was, so an install still checking the old URL sees it once and repoints itself.

**What to do:** run `/phaneslightupgrade`. **Restart your session afterwards**; hooks are snapshotted at session start. Full accounting in [`C