Forge activation (front door)

You are orienting a project where Forge is available (installed as a global plugin or an npm dev-dep) but not yet engaged. Your job is to orient first, then offer — never force. This skill creates nothing by itself; a mutating forge verb is what lazily initializes .forge/.

Orient first (state findings BEFORE offering)

Run read-only checks, then STATE what you found in one short paragraph before you offer any setup. Do not opine or prescribe before you have looked.

1. Is Forge initialized? test -d .forge && echo present || echo absent
2. What kind of project is this?
   • package.json present → JS/TS project (note the package manager: bun/npm/pnpm/yarn lockfile).
   • Markdown-heavy, no package.json → docs / planning repo.
   • Otherwise → describe what you see (language, build files).
3. Is it a git repo? git rev-parse --is-inside-work-tree 2>/dev/null