Templates now have their own command, /trellis-template, and the first web-app template ships with it.
What changed
Applying an optional template is now its own command: /trellis-template lists what is available
and /trellis-template <name> applies one. /trellis-install is back to doing one thing - the base
install - and /trellis-update keeps applied templates current as before.
New web-app template for starting a rogueoak web application from one stack: Next.js 16 (App
Router), TypeScript (strict), Tailwind CSS v4, the @rogueoak/roots design foundation, and the
@rogueoak/canopy design system. Its conventions doc is owned (refreshed on update); the starter
config is yours (seeded once), so an update never clobbers your app.
Breaking
The /trellis-install --template <name> flag is removed. Apply templates with
/trellis-template <name> instead (run /trellis-install first). Repos already on a template need
no change to keep getting updates - /trellis-update still maintains them from the registry.
Under the hood
The copy/registry logic moved into one shipped, tested script (trellis/scripts/template.sh) that
both /trellis-template and /trellis-update call, so apply and update cannot drift. Seed files are
copied per file with an existence check (portable across BSD and GNU cp), and template names are
charset-guarded before any path use.