refactor: make spec auto-sign always-on under /boss, drop the per-project toggle

The auto-sign panel earned its keep: in aura it signed ~20 specs autonomously and discriminates (several recent specs escalated to the human path). The needless complexity was the configuration freedom around it — spec_auto_sign was a per-project toggle that was only ever meant to be on.

Remove the toggle. Auto-sign is now fixed /boss behaviour, with the human sign-off pause as the escalation target (objective gate red / design BLOCK / INFRA_ERROR / budget spent). The panel itself, the Step-1.5 seeding machinery, grounding-check, and the spec-skeptic agent are unchanged; conventions.md can now state there is no per-project behavioural toggle at all.

docs/conventions.md

@@ -96,9 +96,9 @@ configuration. In particular: `brainstorm`, `specify`, `planner`,
 `implement`, `audit`, `debug`, `tdd`, `fieldtest`, and `docwriter` are
 always available. `tdd` is a standard entry path for test-specifiable
 work — not an opt-in. `audit` is mandatory at cycle close.
-`fieldtest` / `docwriter` are orchestrator-dispatched. The single
-behavioural toggle is spec auto-sign under `/boss`, declared (when a
-project wants it) in that project's CLAUDE.md project facts.
+`fieldtest` / `docwriter` are orchestrator-dispatched. There is no
+per-project behavioural toggle: spec auto-sign is always on under
+`/boss`.
 
 ## Per-project facts (in each project's CLAUDE.md)
 
@@ -120,7 +120,6 @@ Under `## Skills plugin: project facts`, where applicable:
 | **fieldtest examples** | fieldtester | Optional path where fixtures are written. |
 | **by-role standing reading** | named agent | Optional; extra files/commands a specific role reads. |
 | **issue tracker** | boss, spec-skeptic | Repo slug + list command + show command (the latter MUST render an issue WITH its comments). |
-| **spec auto-sign** | boss, specify | Optional; `enabled` lets `/boss` sign a spec in the user's place through the auto-sign gate (default: human signature). |
 
 ### Aspirational-source marker (recommendation)
 

docs/design.md

@@ -94,8 +94,8 @@ project's `CLAUDE.md` under `## Skills plugin: project facts`:
 code roots, build / test / lint / doc-build commands, regression
 scripts, architect sweeps, design-ledger / glossary / contracts /
 models / bench / public-interface / fieldtest-examples paths,
-by-role standing reading, the issue-tracker repo slug and commands,
-and spec auto-sign. The template is in
+by-role standing reading, and the issue-tracker repo slug and commands.
+The template is in
 `../templates/CLAUDE.md.fragment`; the per-fact reference is the
 table in `conventions.md`.
 

docs/pipeline.md

@@ -128,10 +128,9 @@ sign-off — with review but no interview. Bounces to `brainstorm` the moment th
 resolve a load-bearing design decision. A core node — the
 spec-production gate before `planner` on every design path.
 
-The sign-off is the user's by default, including under `/boss`. The
-one exception is spec auto-sign (a project that enables it in its
-CLAUDE.md project facts): with it on, a `/boss` run may sign a spec in
-the user's place — but only
+Outside `/boss` the sign-off is the user's. Under `/boss` the
+orchestrator may sign a spec in the user's place through the auto-sign
+gate — but only
 when every objective gate is green AND a unanimous five-lens
 `spec-skeptic` panel passes; the orchestrator's own confidence never
 signs. A `BLOCK` is never signed over: an editorial one (`criterion` /
@@ -288,9 +287,9 @@ dispatch shown above are fixed — the same for every project. All
 phases (`brainstorm`, `specify`, `planner`, `implement`, `audit`,
 `debug`, `tdd`, `fieldtest`, `docwriter`) are always available; which
 ones run on a given iteration is the orchestrator's judgement per the
-skip rules above, not a per-project setting. The only behavioural
-toggle is spec auto-sign under `/boss`, declared in a project's
-CLAUDE.md project facts. See `conventions.md`.
+skip rules above, not a per-project setting. There is no behavioural
+toggle either: spec auto-sign is always on under `/boss`. See
+`conventions.md`.
 
 If a project declares a glossary in its CLAUDE.md project facts, that
 file is standing reading for every role — the canonical-nomenclature