refactor: make ARNES external-repo based with ticket publish flow

starter-pack/README.md

@@ -4,15 +4,15 @@ Este pack sirve para arrancar ARNES en 2 escenarios:
 
 ## A) Proyecto nuevo (greenfield)
 1. Crea repo vacío.
-2. Copia el template ARNES.
+2. Instala el core ARNES desde otro repo fuente (`scripts/install_into_repo.sh`).
 3. Ajusta `backlog/features.json` (`project`, `description`).
-4. Copia `starter-pack/backlog.features.bootstrap.json` como primera feature.
+4. Copia `starter-pack/backlog.features.bootstrap.json` como primera feature (`type=chore`).
 5. Ejecuta:
    - `./scripts/verify.sh`
    - `python3 scripts/agent_status.py show`
 
 ## B) Proyecto ya empezado (brownfield)
-1. Copia **solo** carpetas core ARNES: `harness/`, `spec/`, `backlog/`, `work/`, `scripts/`, `platforms/`.
+1. Instala **solo** el core ARNES dentro del repo existente.
 2. Mantén tu código actual intacto.
 3. Añade checks del dominio en `scripts/verify.local.sh`.
 4. Define features reales del proyecto en `backlog/features.json`.
@@ -22,5 +22,7 @@ Este pack sirve para arrancar ARNES en 2 escenarios:
 
 ## Reglas mínimas
 - 1 sola feature en `in_progress`.
+- Tipos válidos: `feature`, `fix`, `bug`, `chore`.
 - `done` requiere gates: `review/security/qa`.
+- `done` requiere commit+push final del ticket.
 - Evidencia en `work/artifacts/<feature_id>/`.

starter-pack/backlog.features.bootstrap.json

@@ -1,11 +1,25 @@
 {
   "id": "F-001",
-  "title": "Bootstrap de proyecto con ARNES",
-  "description": "Configurar pipeline SDD en este repositorio y validar primer ciclo completo.",
+  "type": "chore",
+  "title": "Bootstrap ARNES on project",
+  "problem": "Need base workflow and control",
+  "goal": "Make ARNES ready on this repo",
+  "scope_in": [
+    "Harness setup",
+    "Runtime status",
+    "First verify cycle"
+  ],
+  "scope_out": [
+    "Business feature work",
+    "Product redesign"
+  ],
+  "priority": "med",
+  "risk": "low",
+  "description": "Problem: Need base workflow and control. Goal: Make ARNES ready on this repo. Scope IN: Harness setup, Runtime status, First verify cycle. Scope OUT: Business feature work, Product redesign. Type: chore. Priority: med. Risk: low.",
   "acceptance": [
-    "verify.sh en verde",
-    "runtime-status operativo",
-    "primera feature cerrada con gates"
+    "verify.sh is green",
+    "runtime status works",
+    "first feature closes with gates"
   ],
   "status": "pending",
   "created_at": "YYYY-MM-DD",