scrumrun 1.5.0

package/templates/project/.scrumrun/golden-rules.md

@@ -0,0 +1,9 @@
+# Golden Rules - {{PROJECT_NAME}}
+
+Golden rules are absolute. If a golden rule conflicts with any other instruction, the golden rule wins.
+
+## Rules
+
+1. Never commit real secrets.
+2. Runtime-specific values must come from env/config.
+3. Never modify read-only source paths.

package/templates/project/.scrumrun/knowledge.md

@@ -0,0 +1,15 @@
+# Knowledge Base - {{PROJECT_NAME}}
+
+Only approved knowledge should be used as planning context for `/sc-challenge`, `/sc-sprint --new`, `/sc-sprint --run`, and feature planning.
+
+## Approved Knowledge
+
+- Pending: none.
+
+## Pending Proposals
+
+- Pending: none.
+
+## Rejected Proposals
+
+- Pending: none.

package/templates/project/.scrumrun/map.md

@@ -0,0 +1,20 @@
+# Project Map - {{PROJECT_NAME}}
+
+Generated: {{DATE}}
+
+## Purpose
+
+This file is a compact navigation aid for agents. It is not a source of truth. Verify paths before editing code.
+
+## Top-Level Structure
+
+- `AGENTS.md` — root agent instructions.
+- `.scrumrun/` — ScrumRun project memory, plans, histories, decisions, and reviews.
+
+## Important Commands
+
+- Pending: run `/scr-map --build` after project files exist.
+
+## Notes
+
+- Update this file when important folders, modules, commands, routes, or config files are added or moved.

package/templates/project/.scrumrun/project.md

@@ -0,0 +1,26 @@
+# Project - {{PROJECT_NAME}}
+
+Created: {{DATE}}
+
+## Purpose
+
+Pending: define the product or system goal with `/scr-goal --new`.
+
+## Stack
+
+Pending: detect or confirm language, framework, database, deployment, test tooling, and integrations.
+
+## Architecture
+
+Pending: define architecture style and important boundaries.
+
+## Active Lanes
+
+- Main goal: `.scrumrun/goals/main/`
+- Features: `.scrumrun/features/`
+
+## Safety Boundaries
+
+- Never commit real secrets.
+- Runtime-specific values must come from env/config.
+- Read-only source paths: pending confirmation.

package/templates/project/.scrumrun/reviews/.gitkeep

@@ -0,0 +1 @@
+

package/templates/project/.scrumrun/runbook.md

@@ -0,0 +1,101 @@
+# ScrumRun Runbook
+
+## Purpose
+
+This runbook lets an AI agent execute one sprint independently and safely.
+
+## Natural-Language Intake
+
+When the owner describes work without a ScrumRun command and `Interaction Mode` is not `strict`:
+
+1. Identify the intent, expected outcome, urgency, scope, risk, and relationship to the main goal.
+2. Read only the canonical context and relevant history needed to verify the classification.
+3. Route the request to one of: quick task, knowledge/discovery, main sprint, corrective fix, backlog, isolated feature lane, or reject/defer.
+4. Present the recommendation, rationale, material unknowns, and at most two useful alternatives.
+5. Ask for approval when required by `.scrumrun/config.md`; otherwise state which configured policy authorizes the transition.
+6. Only after approval, invoke the matching workflow and preserve its normal safety rules.
+
+Intake may think and recommend autonomously. It must not interpret a vague acknowledgement as permission to execute application changes.
+
+## Required Start Sequence
+
+1. Read `AGENTS.md`.
+2. Read `.scrumrun/golden-rules.md`.
+3. Read `.scrumrun/config.md`.
+4. Read `.scrumrun/token-policy.md`.
+5. Read `.scrumrun/context.md` as a snapshot, not truth.
+6. Read `.scrumrun/map.md`.
+7. Read `.scrumrun/project.md` and `.scrumrun/knowledge.md`.
+8. Read `.scrumrun/runbook.md`.
+9. Read the relevant sprint plan:
+   - main goal: `.scrumrun/goals/main/sprint.md`
+   - feature lane: `.scrumrun/features/<feature>/sprint.md`
+10. Read the relevant history file.
+11. Check whether the requested sprint already has `Status: completed.`, `Status: partial.`, or `Status: blocked.`.
+12. If it already ran, ask whether to audit, rerun/fix, resume, or continue to another sprint.
+13. Identify dependencies, impacted files, env/config impact, database impact, and test plan.
+14. Only then implement.
+
+## Sprint Analysis Template
+
+```text
+Sprint:
+Lane: main goal | feature <slug>
+History status:
+Goal:
+Relevant docs/specs:
+Source areas to audit:
+External docs needed:
+Expected files:
+Env/config impact:
+Database impact:
+Test plan:
+Open questions:
+```
+
+## Execution Protocol
+
+1. Entenda
+2. Avalie Impactos
+3. Tire Duvidas
+4. Execute
+5. Teste
+
+## Safety Rules
+
+- Never modify read-only source paths.
+- Never commit real secrets.
+- Use env/config for runtime values.
+- Ask before changing behavior that is ambiguous or production-sensitive.
+- Use mocks/fakes for external providers in automated tests.
+- Keep main goal and feature lane histories separate.
+- Update `.scrumrun/context.md` when sprint execution changes current focus, risks, decisions, or map pointers.
+
+## History Update Template
+
+```md
+### YYYY-MM-DD - Sprint NN: Name
+
+Status: completed|partial|blocked
+
+Summary:
+- ...
+
+Files changed:
+- ...
+
+Commands run:
+- ...
+
+Tests/verification:
+- ...
+
+Env/config:
+- Added variable names only, no values: ...
+
+Decisions:
+- ...
+
+Risks/follow-ups:
+- ...
+```

package/templates/project/.scrumrun/token-policy.md

@@ -0,0 +1,43 @@
+# ScrumRun Token Policy - {{PROJECT_NAME}}
+
+This policy reduces token waste without weakening ScrumRun safety.
+
+## Rules
+
+1. Safety beats token economy. Never skip `core.md`, `golden-rules.md`, `config.md`, or relevant history to save tokens.
+2. `context.md` is a snapshot, not truth. Use it to choose what to read, then verify against canonical files.
+3. Prefer targeted reads over broad dumps. Read specific files, symbols, folders, and ranges when possible.
+4. Prefer summaries for large logs, generated output, dependency folders, old reviews, and old history.
+5. Do not read `.scrumrun/vault.local.md` unless the user explicitly asks for a local development credential workflow.
+6. Do not print vault values in summaries, context, history, decisions, reviews, or commits.
+7. Use `map.md` before repeated broad searches.
+8. Use approved knowledge before planning. Pending knowledge is not planning truth.
+9. When a source is skipped for token economy, say what was skipped and why.
+10. If uncertainty affects correctness or safety, read the source even if it costs more tokens.
+
+## Recommended Read Order
+
+```text
+AGENTS.md
+  -> core.md
+  -> golden-rules.md
+  -> config.md
+  -> token-policy.md
+  -> context.md
+  -> map.md
+  -> project.md
+  -> knowledge.md
+  -> runbook.md
+  -> current backlog / sprint / feature files
+  -> agents.md
+  -> relevant history + decisions
+  -> targeted source files
+```
+
+## Output Discipline
+
+- Summarize command output.
+- Include exact file references when they matter.
+- Avoid pasting large diffs unless requested.
+- For tests, report command, result, and relevant failures only.
+- For reviews, list findings by severity before summaries.

package/templates/project/AGENTS.md

@@ -0,0 +1,59 @@
+# AGENTS.md - {{PROJECT_NAME}}
+
+## ScrumRun
+
+This project uses ScrumRun.
+
+ScrumRun is mandatory in this project. Slash commands are optional shortcuts; the methodology is not optional.
+
+Before planning, executing, auditing, or reviewing work, read:
+
+1. `.scrumrun/core.md` — portable ScrumRun method and command equivalents.
+2. `.scrumrun/golden-rules.md` — **MANDATORY. Highest priority. Never violate.**
+3. `.scrumrun/config.md` — response language and ScrumRun behavior preferences.
+4. `.scrumrun/token-policy.md` — context economy rules.
+5. `.scrumrun/context.md` — token-safe snapshot, not source of truth.
+6. `.scrumrun/map.md` — project folders, paths, modules, and key files.
+7. `.scrumrun/project.md`
+8. `.scrumrun/knowledge.md`
+9. `.scrumrun/runbook.md` — execution protocol before reading operational work.
+10. `.scrumrun/backlog.md`
+11. `.scrumrun/goals/main/sprint.md`
+12. `.scrumrun/agents.md`
+13. `.scrumrun/goals/main/history.md`
+14. `.scrumrun/goals/main/decisions.md`
+
+If the current AI client does not support `/sc-*` slash commands, read `.scrumrun/core.md` and execute the matching ScrumRun workflow manually.
+
+If the user asks for work without mentioning ScrumRun, still follow ScrumRun because this project was initialized with it.
+
+Unless `.scrumrun/config.md` sets `Interaction Mode: strict`, treat natural-language requests for fixes, features, refactors, investigations, or product changes as ScrumRun intake. Classify the request, recommend the safest workflow, and obtain the approval required by `.scrumrun/config.md` before creating operational records or changing application code. The user does not need to know or invoke a slash command.
+
+## Absolute Safety Rules
+
+- Do not start a sprint unless the owner explicitly asks for that sprint.
+- Do not convert an intake recommendation into a backlog item, sprint, feature lane, fix, or code change until the configured approval gate is satisfied.
+- Before executing any main-goal sprint, check `.scrumrun/goals/main/history.md`.
+- Before executing any feature sprint, check that feature lane's `history.md`.
+- If a sprint is `completed`, ask whether to audit, rerun/fix, or continue to the next sprint.
+- If a sprint is `partial` or `blocked`, ask whether to resume, audit, or move to another sprint.
+- Never commit real secrets.
+- Runtime-specific values must come from env/config, not hardcoded strings.
+- If a project has a read-only source path, never modify it.
+- Keep main goal history and feature lane history separate.
+- Use `.scrumrun/context.md` to reduce unnecessary reading, but never as canonical truth.
+- If context conflicts with golden rules, approved knowledge, history, decisions, or source code, context loses.
+
+## Sprint Protocol
+
+Every sprint must follow:
+
+1. Entenda
+2. Avalie Impactos
+3. Tire Duvidas
+4. Execute
+5. Teste
+
+## Handoff
+
+At the end of each sprint, update the relevant history file with status, files changed, commands run, tests, decisions, env variable names, risks, and follow-ups.