dna-sdk 0.1.0

package/dist/extensions/sdlc/kinds/workflow-event.kind.yaml

@@ -0,0 +1,195 @@
+# WorkflowEvent — append-only journey ledger of phase transitions (record plane).
+#
+# One entry per (artifact, phase) pair: the trail from discover → reflect for
+# a Roadmap/Epic/Feature, with explicit honesty about skipped phases. DNA's
+# methodology-agnostic layer — Superpowers/BMAD/Spec Kit map onto it via
+# `methodology`. Distinct from `<Kind>.spec.journey_phase` (one doc, one
+# phase): the WorkflowEvent IS the transition entry.
+#
+# F3 lote-1 (spec 2026-06-10-kinds-descriptor-f3): synthesized from this
+# descriptor; the twin WorkflowEventKind classes (Py+TS) were deleted.
+# PARITY-CRITICAL package data — byte-identical mirror under
+# packages/sdk-{py,ts}; tests/test_descriptor_hash_parity.py enforces.
+# Equivalence vs the extinct class frozen in
+# tests/test_lote1_descriptor_equivalence.py (summary projeta null quando o
+# campo falta — semântica da classe Py preservada; o resumo TS antigo
+# divergia com defaults "" e foi unificado pro canônico).
+# Strictness: additionalProperties:false preservado — sdlc-workflow-event é
+# o kind-âncora strict do ratchet test_strict_schema_lint.
+apiVersion: github.com/ruinosus/dna/core/v1
+kind: KindDefinition
+metadata:
+  name: workflow-event
+spec:
+  target_api_version: github.com/ruinosus/dna/sdlc/v1
+  target_kind: WorkflowEvent
+  alias: sdlc-workflow-event
+  origin: github.com/ruinosus/dna/sdlc
+  tenant_scope: global
+  plane: record
+  prompt_target: false
+  flatten_in_context: false
+  prompt_target_priority: 0
+  storage:
+    type: yaml
+    container: journey
+  dep_filters:
+    ref: sdlc-spec|sdlc-plan|sdlc-story|sdlc-feature|sdlc-epic|sdlc-roadmap|sdlc-agent-session|sdlc-narrative
+    parent_ref: sdlc-spec|sdlc-plan|sdlc-story|sdlc-feature|sdlc-epic|sdlc-roadmap|sdlc-agent-session|sdlc-narrative
+    transitioned_from: sdlc-workflow-event
+  schema:
+    type: object
+    required:
+    - phase
+    properties:
+      phase:
+        type: string
+        enum:
+        - discover
+        - specify
+        - plan
+        - build
+        - verify
+        - reflect
+        description: Which of the five universal phases this entry represents.
+      ref:
+        type: string
+        description: 'Doc this entry pins. Format: ``Kind/name`` (e.g. ``Spec/foo``,
+          ``Plan/bar``, ``AgentSession/vs-baz``).'
+      parent_ref:
+        type: string
+        description: Anchor doc grouping this entry with siblings. Typically ``Feature/<name>``
+          or ``Epic/<name>`` — everything in the journey of one Feature has the
+          same parent_ref.
+      transitioned_from:
+        type: string
+        description: Name of the previous WorkflowEvent in this trajectory (forms
+          a linked list). Optional for the first entry of a trajectory.
+      seed_from:
+        type: string
+        description: 'Name of the prior cycle''s `reflect` WorkflowEvent that seeded
+          this entry. Set on `discover` entries created via `dna sdlc journey close-cycle`
+          — the ouroboros bite, where reflect''s lessons literally feed into the
+          next discover. Distinct from `transitioned_from`: that''s the immediate
+          predecessor across phases; this is the cross-cycle inheritance link.'
+      cycle_index:
+        type: integer
+        minimum: 1
+        description: 1-based cycle number this entry belongs to. All entries within
+          the same ouroboros loop share the same cycle_index. Incremented when `journey
+          close-cycle` opens the next discover. Backend-explicit alternative to
+          client-side heuristic cycle detection.
+      closes_cycle:
+        type: boolean
+        description: True on a `reflect` entry that has been closed by `journey
+          close-cycle` — marks the boundary where the next discover starts cycle
+          N+1. Set automatically; client may use as the explicit cycle delimiter.
+      started_at:
+        type: string
+        format: date-time
+      ended_at:
+        type: string
+        format: date-time
+        description: When the agent left this phase. Null while the phase is still
+          active.
+      methodology:
+        type: string
+        enum:
+        - superpowers
+        - bmad
+        - spec-kit
+        - kiro
+        - rfc
+        - adr
+        - ad-hoc
+        - custom
+        description: Which methodology the agent followed in this phase. ``ad-hoc``
+          is honest — Studio renders it with a 'no methodology' badge so we can
+          spot where we cut corners.
+      methodology_artifact:
+        type: string
+        description: Repo-relative path or URL to the methodology's external artifact,
+          when applicable. E.g. ``docs/superpowers/plans/foo-plan.md`` for the Superpowers
+          writing-plans output, ``.specify/foo/plan.md`` for Spec Kit, etc.
+      skipped_phases:
+        type: array
+        items:
+          type: string
+          enum:
+          - discover
+          - specify
+          - plan
+          - build
+          - verify
+          - reflect
+        description: Phases jumped over to get to this entry. E.g. discover → build
+          means skipped ['specify', 'plan'] — Studio shows them in muted strikethrough
+          so the trajectory stays honest.
+      actor:
+        type: string
+        description: Who recorded the transition.
+      summary:
+        type: string
+        description: 1-2 sentence note about what happened in this phase. Optional
+          — rendered as the entry's tooltip in Studio.
+      tags:
+        type: array
+        items:
+          type: string
+      created_at:
+        type: string
+        format: date-time
+      # --- Back-compat (i-144): pre-redesign journey shape. ~1574 historical
+      # entries predate the phase+ref model — they use artifact_kind/artifact_name
+      # instead of ``ref``, auto_emitted_by instead of ``actor``, timestamp instead
+      # of ``created_at``, feature_ref/epic_ref instead of ``parent_ref``. Kept
+      # OPTIONAL (and ``ref`` dropped from required) so they validate under the
+      # strict additionalProperties:false; NEW entries use the canonical fields.
+      artifact_kind:
+        type: string
+        description: 'Back-compat (deprecated): legacy Kind half of ``ref``.'
+      artifact_name:
+        type: string
+        description: 'Back-compat (deprecated): legacy name half of ``ref``.'
+      auto_emitted_by:
+        type: string
+        description: 'Back-compat (deprecated): legacy form of ``actor``.'
+      timestamp:
+        type: string
+        description: 'Back-compat (deprecated): legacy form of ``created_at``.'
+      decision_text:
+        type: string
+        description: 'Back-compat (deprecated): free-text decision on the entry.'
+      rationale:
+        type: string
+        description: 'Back-compat (deprecated): free-text rationale on the entry.'
+      owner:
+        type: string
+        description: 'Back-compat (deprecated): legacy owner of the entry.'
+      feature_ref:
+        type: string
+        description: 'Back-compat (deprecated): legacy form of ``parent_ref`` (Feature).'
+      epic_ref:
+        type: string
+        description: 'Back-compat (deprecated): legacy form of ``parent_ref`` (Epic).'
+      decisions:
+        type: string
+        description: 'Back-compat (deprecated): legacy decisions note on the entry.'
+    additionalProperties: false
+  summary:
+    phase: null
+    ref: null
+    parent_ref: null
+    methodology: null
+    started_at: null
+    ended_at: null
+  graph_style:
+    fill: '#0EA5E9'
+    stroke: '#0284C7'
+    text_color: '#fff'
+  ascii_icon: 🧭
+  display_label: Journey Entries
+  docs: Append-only journey ledger. One entry per (artifact, phase) pair. Read together
+    as a sequence, they form the trail from discover → reflect for a Roadmap/Epic/Feature.
+    DNA's methodology-agnostic layer — Superpowers / BMAD / Spec Kit all map onto
+    it via the `methodology` field.

package/dist/extensions/sdlc.d.ts

@@ -0,0 +1,32 @@
+/**
+ * SdlcExtension — software-development lifecycle Kinds.
+ *
+ * Seven Kinds for declarative product/engineering management as YAML/markdown:
+ *
+ *   - Roadmap (sdlc-roadmap) — top-level, lists epics across horizons
+ *   - Epic (sdlc-epic) — Jira/ADO-aligned aggregation umbrella; optional target date
+ *   - Feature (sdlc-feature) — shippable unit; implements UseCases
+ *   - Story (sdlc-story) — granular task with owner + estimate
+ *   - Issue (sdlc-issue) — bug/enhancement/question/task; can link to a Finding
+ *   - Spec (sdlc-spec) — top-level design artifact (ADR-style)
+ *   - Plan (sdlc-plan) — implementation plan, child of a Spec
+ *
+ * 1:1 parity with Python ``dna.extensions.sdlc`` for the KIND
+ * surface (registration, descriptors, schemas, write-guards).
+ *
+ * Known Py-only helpers (verified 2026-07-08, s-dna-sdlc-cli-extraction —
+ * documented here on purpose, not silently): ``journey_derive.py`` (the
+ * derived per-work-item journey computation consumed by the server journey/
+ * focus routes and the CLI) and ``work_item_outputs.py`` (produces[]
+ * resolution) have NO TS twin. They are pure read-side helpers OVER Kind
+ * data, not Kind behavior — port them when a TS consumer needs the derived
+ * journey, and add their members to the parity fixtures at that point.
+ *
+ * v1.3 BREAKING: Milestone Kind renamed to Epic.
+ */
+import type { ExtensionHost, Extension } from "../kernel/protocols.js";
+export declare class SdlcExtension implements Extension {
+    readonly name = "sdlc";
+    readonly version = "1.14.0";
+    register(kernel: ExtensionHost): void;
+}