learnship 2.0.3 → 2.0.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "learnship",
   "description": "Agentic engineering done right — 49 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system. Works with Claude Code, Windsurf, Cursor, Gemini CLI, OpenCode, and Codex.",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "author": {
     "name": "Favio Vazquez",
     "email": "favio.vazquezp@gmail.com"

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "learnship",
   "displayName": "learnship",
   "description": "Agentic engineering done right — 49 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "logo": "assets/logo.png",
   "author": {
     "name": "Favio Vazquez",

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "learnship",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "description": "Agentic engineering done right — 49 structured workflows, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
   "author": "Favio Vazquez",
   "homepage": "https://faviovazquez.github.io/learnship/",

package/learnship/workflows/new-milestone.md

@@ -133,12 +133,16 @@ If yes: merge missing keys into `.planning/config.json` using the defaults from
 
 ## Step 7: Research Decision
 
+> **🔴 MANDATORY USER CHOICE — You must ask this question and wait for a reply. You are NOT allowed to decide this yourself, even if the domain seems trivial, familiar, or well-understood. The user decides. Always.**
+
 Read `workflow.research` from `.planning/config.json`.
 
-Ask: "Research the domain for the new features before defining requirements?"
+Ask: **"Research the domain for the new features before defining requirements?"**
 - **Research first** (recommended) — investigate new capabilities' ecosystem
 - **Skip research** — domain is familiar
 
+> 🛑 STOP. Wait for the user's explicit choice. Do not default to either option. Do not reason about whether research is needed — that is the user's call. Do not proceed until the user replies.
+
 Update config accordingly:
 ```bash
 # Edit .planning/config.json: set workflow.research to true or false

package/learnship/workflows/new-project.md

@@ -275,11 +275,13 @@ git add .planning/PROJECT.md && git commit -m "docs: initialize project"
 
 ## Step 5: Research Decision
 
+> **🔴 MANDATORY USER CHOICE — You must ask this question and wait for a reply. You are NOT allowed to decide this yourself, even if the domain seems trivial, familiar, or well-understood. The user decides. Always.**
+
 Ask: **"Before I write the requirements — do you want me to research the domain ecosystem first?"**
 - **Research first** (recommended) — Discover standard stacks, expected features, architecture patterns
 - **Skip research** — I know this domain well, go straight to requirements
 
-> 🛑 STOP. Wait for the user's explicit choice. Do not default to either option. Do not write REQUIREMENTS.md yet. Do not proceed until the user replies.
+> 🛑 STOP. Wait for the user's explicit choice. Do not default to either option. Do not reason about whether research is needed — that is the user's call. Do not write REQUIREMENTS.md yet. Do not proceed until the user replies.
 
 **If Research first:**
 
@@ -394,9 +396,26 @@ git add .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md && git
 
 > **🔴 MANDATORY — This step must always be completed. Do not skip it, do not defer it, do not move to Step 9 without writing AGENTS.md to the project root. AGENTS.md is the persistent memory file that every future session depends on.**
 
-Copy `@./templates/agents.md` to the project root as `AGENTS.md`.
+Start by reading `@./templates/agents.md` in full. This is the **canonical template**. The generated AGENTS.md must follow its exact structure.
+
+**Sections to copy VERBATIM (do not rewrite, do not summarize, do not rephrase):**
+- `## Soul — Who We Are Together` (entire section including Voice & Character and Relationship Model)
+- `## Principles — How We Operate` (all 10 principles, verbatim)
+- `## Platform Context` (the learnship key facts block, verbatim)
+- `## Skills — Operational Knowledge` (CHANGELOG Discipline and Decisions Register, verbatim)
+- `## Regressions — What Broke and What We Learned` (the empty starter block, verbatim)
+
+**Sections to FILL IN with project-specific information:**
 
-Fill in the placeholder sections using information gathered in this session:
+**Title** — Replace `[PROJECT NAME]` with the actual project name.
+
+**Current Phase** block:
+```
+Milestone: v1.0 — [Milestone Name from PROJECT.md]
+Phase: 1 — [Phase 1 name from ROADMAP.md]
+Status: planning
+Last updated: [today's date]
+```
 
 **Project Structure** — derive from the project description and any existing directories:
 ```bash
@@ -413,13 +432,18 @@ Populate the `## Project Structure` tree with real directories and one-line desc
 - How to run the dev server
 - How to run tests
 
-**Current Phase** block:
-```
-Milestone: v1.0 — [Milestone Name from PROJECT.md]
-Phase: 1 — [Phase 1 name from ROADMAP.md]
-Status: planning
-Last updated: [today's date]
-```
+**You may ADD project-specific sections** (e.g., Conventions, Content Sources, Definition of Done) **after** the Tech Stack section and **before** Skills. But you must NEVER remove, rename, or replace the template sections listed above.
+
+**Verification checklist (run before committing):**
+- [ ] File starts with `# AGENTS.md — [Project Name]`
+- [ ] `## Soul — Who We Are Together` exists with Voice & Character and Relationship Model
+- [ ] `## Principles — How We Operate` exists with all 10 numbered principles
+- [ ] `## Platform Context` exists with the 7-step phase loop
+- [ ] `## Current Phase` exists with milestone, phase, status, and date
+- [ ] `## Project Structure` exists with a directory tree
+- [ ] `## Tech Stack` exists with language, framework, libraries, dev server, tests
+- [ ] `## Skills — Operational Knowledge` exists with CHANGELOG Discipline and Decisions Register
+- [ ] `## Regressions — What Broke and What We Learned` exists at the end
 
 **If `commit_mode` is `auto`:**
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "learnship",
-  "version": "2.0.3",
+  "version": "2.0.4",
   "description": "Learn as you build. Build with intent. — A multi-platform agentic engineering system for Windsurf, Claude Code, Cursor, OpenCode, Gemini CLI, and Codex: spec-driven workflows, integrated learning, and production-grade design.",
   "keywords": [
     "agentic",