chore(release): 1.0.0 (#17)

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.

0.4.1: feat(templates): unify What's new into the plugin-release pipeline (#14)

The release pipeline now refreshes the README "What's new" automatically, and ships that as part of the template.

What changed

0.4.0 automated tag + Release, but the README "What's new" headline never updated - dogfooding
exposed two reasons: a GITHUB_TOKEN-created Release does not fire release: published workflows,
and the old whats-new.yml pushed directly to a ruleset-protected main.

The plugin-release template now owns the whole pipeline. whats-new.yml triggers on workflow_run
of the Release workflow (so it survives the token-recursion rule) and lands the README headline
through an auto-merged PR (so a protected main is fine). It uses one canonical, dependency-free
whats-new.sh with neutral <!-- whats-new:start/end --> markers, so every consumer runs the same
one.

Dogfood

Trellis re-adopts the unified pipeline and cuts this 0.4.1 release through it - the headline you are
reading was refreshed automatically.

0.4.0: feat(templates): optional templates + a plugin-release template (#13)

Optional templates, and a plugin-release template for single-source versioning and automated releases.

What changed

Trellis can now ship optional templates - opt-in bundles a repo installs with
/trellis-install --template <name>, kept current thereafter by plain /trellis-update. Unlike
rules (which every Trellis repo follows), a template applies only to repos that want it.

The first template is plugin-release, for repos that are themselves published marketplace
plugins:

• A root VERSION file is the single source of truth; scripts/bump-version.sh rewrites it and
  every manifest listed in .version-manifests together, and --check fails CI on any drift.
• A standalone .github/workflows/release.yml tags the version and publishes a GitHub Release
  once your CI workflow succeeds on main - composing with the existing "What's new" automation.

Each template splits into owned/ (Trellis refreshes these on update) and seed/ (copied once,
then yours), so an update can never clobber your content. See trellis/templates/README.md.

Dogfood

Trellis adopts plugin-release for its own seven manifests (previously hand-synced at 0.3.0),
adds a CI workflow that runs its test suites and the version-sync guard, and cuts this 0.4.0
release through the new pattern.

0.3.0

Every repo now ships a LICENSE, README, and CONTRIBUTING, with a standard README layout.

What's new

• New guidelines rule. A "Repo structure" rule: every repo ships a LICENSE, README.md, and CONTRIBUTING.md, and the README follows a standard section layout (title image + tagline, badges, brief description, quick start, what's new, optional documentation, license).
• README. New tagline; the What's new block is reformatted and reordered below Quick start to match the template.
• CONTRIBUTING.md added for this repo.
• AGENTS.md notes that this repo is the Trellis source: edit Trellis's own rules, never Spectra's vendored protocol.

Full changelog: 0.2.0...0.3.0

0.2.0

Install and update now bring your repo into compliance, not just carry the rules.

/trellis-install and /trellis-update run a compliance pass over your tracked text and report any violation of a mechanically-checkable rule as file:line. Today that is guidelines.md's em/en-dash ban.

• Reports by default and changes nothing. Run /trellis-install --fix to rewrite em/en dashes to ASCII, then review the diff.
• Non-blocking: a repo with violations still finishes installing, with a list to clean up.
• One dependency-free POSIX sh script both commands call, verified under dash, reusable later by a pre-commit hook or CI.
• A developer-owned docs/rules/.compliance-ignore skips content another tool vendors (for example docs/spectra/).

0.1.2

Relax the writing rule: ban only em/en dashes, allow meaningful Unicode (arrows, math symbols, ellipsis, section refs, emoji).

0.1.1 - Trellis

A small rules release.

What changed since 0.1.0

• New rule: tag releases with a Semantic Versioning number and no v prefix (0.1.1, not v0.1.1). See docs/rules/guidelines.md.

Run /trellis-update in your repo to pull the updated rules.

0.1.0 - Trellis

The first release of Trellis - rogueoak's shared AI-agent conventions, installable into any repo.

What you get

• Install in one command. Add the marketplace, install the plugin, run /trellis-install. Your rules land in docs/rules/ and your AGENTS.md points agents at them. /trellis-update keeps them current.
• Cross-agent. Packaged for Claude Code, OpenAI Codex, Gemini CLI, and Cursor.
• Two rules to start:
  • guidelines.md - ASCII-only writing; tests, lint, and build green before merge; every PR comment resolved before merge; Conventional Commit messages.
  • language.md - the voice for public-facing writing (warm, specific, terse, no hype).
• Commit-msg enforcement. A dependency-free POSIX hook checks Conventional Commit format with nothing to install. It displaces and chains onto any existing hook, and warns if a hook manager would shadow it.
• Pairs with Spectra. Trellis is the conventions; Spectra is the process. Install both; they stay independent.

Quick start (Claude Code)

/plugin marketplace add rogueoak/trellis
/plugin install trellis@trellis
/reload-plugins
/trellis-install

See the README for Codex, Gemini, and Cursor.