raptor-aios 0.1.0 → 0.3.0

package/CHANGELOG.md

@@ -3,9 +3,39 @@
 All notable changes to this project will be documented in this file.
 Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [0.3.0] - 2026-06-04
+
+### Fixed
+
+- **`raptor new --jira=<KEY>` now seeds a reused-but-unseeded feature.** The Jira fetch was gated behind `!reusing`, so re-running `new` over a half-created feature directory (the folder existed but `spec.md` had never been written) silently skipped the fetch and left the spec empty (`id only (fetch unavailable)`). The trigger is now the absence of `spec.md`, not the reuse flag: `new` always consults Jira when it is about to seed and a ticket was given, and re-seeds any missing `spec.md` in an existing directory — without ever overwriting an already-authored spec or truncating companion files.
+
+### Added
+
+- **Full Jira context lands in the spec, in canonical form.** The seeded `spec.md` carries the complete ticket body verbatim, and both the `spec.md.hbs` template and the `/raptor-specify` command now instruct the agent to redistribute every imported user story, functional/non-functional requirement, acceptance scenario, out-of-scope item, and design link into its canonical section — losing nothing — then reduce the Problem Statement to a crisp who/how.
+- **`/raptor-specify` no longer clobbers a seeded spec:** when `spec.md` already holds real content (e.g. seeded by `raptor new`), the command authors in place instead of copying the blank template over it.
+
+### Security
+
+- Jira/Confluence secrets stay out of `raptor.yml`: the MCP `env` block supports `${VAR}` expansion against the shell environment (e.g. `JIRA_API_TOKEN: ${ATLASSIAN_API_TOKEN}`), so committed configs reference a token held in the environment instead of embedding it.
+
+## [0.2.0] - 2026-06-03
+
+### Added
+
+- **Spec workflow of excellence:** the spec is now born populated. `raptor new -d/--desc "<descrição>"` captures a natural-language description that seeds the `Summary` and the agent prompt instead of an empty skeleton.
+- **Single canonical spec template:** `templates/spec-template.md` and `packages/core/templates/spec.md.hbs` now share one rich form (Summary, Problem Statement, User Scenarios, User Stories with priority/why/independent-test, `FR-###`, Key Entities, NFRs, Edge Cases, Out of Scope, Dependencies & Assumptions, `AC-###`, technology-agnostic `SC-###`, dated Clarifications, and an embedded Review & Acceptance Checklist).
+- **`gate.spec.ready`:** new built-in gate enforcing spec cohesion (every user story covered by an acceptance criterion, AC ids mirrored in frontmatter, measurable success criteria, no leftover placeholders).
+
+### Changed
+
+- **`/raptor-specify` (v2.0.0):** informed-defaults table, hard cap of 3 high-impact `[NEEDS CLARIFICATION]` markers (ranked scope → security → UX → feasibility), evidence-based self-validation loop, and a richer `checklists/requirements.md`.
+- **`/raptor-clarify` (v2.0.0):** investigative clarification — 9-category coverage map, Impact×Uncertainty prioritization, ≤5 recommendation-driven questions, section-aware integration, and before→after checklist re-validation.
+- **README:** rewritten for first-time users (per-command guidance, React Native flow, Mermaid diagrams, tables); removed Spec Kit references.
+
 ## [0.1.0] - 2026-04-24
 
 ### Added
+
 - **Full SDD Lifecycle:** `new` → `clarify` → `plan` → `tasks` → `implement` → `analyze` → `checklist` with mandatory gate enforcement between phases.
 - **Workflow Engine:** Declarative YAML-based workflow orchestration with resumable state machine, conditional steps, loops, branches, fan-out/fan-in, and human gates.
 - **Real Shell Executor:** `child_process.spawn`-based async shell execution with configurable timeout (default 30s), environment injection, and stream-based stdout/stderr capture. Replaces the previous `execSync` blocking implementation.
@@ -21,6 +51,7 @@ Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **593 Tests:** 467 core + 126 CLI, 0 failures.
 
 ### Infrastructure
+
 - Monorepo: `@raptor/core` + `@raptor/cli` via pnpm workspaces.
 - TypeScript strict mode, ESM (NodeNext), Node.js ≥ 20.
 - Oclif-based CLI with dynamic command loading.