sddflow 2.7.74__tar.gz → 2.7.82__tar.gz

{sddflow-2.7.74 → sddflow-2.7.82}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sddflow
-Version: 2.7.74
+Version: 2.7.82
 Summary: SDD Framework CLI — initialize and upgrade Spec-Driven Development packs
 Project-URL: Homepage, https://github.com/sunil1983us/universalguide
 Project-URL: Repository, https://github.com/sunil1983us/universalguide
@@ -574,6 +574,7 @@ Shows, per feature under `.specify/features/`:
     BRD"), which would misleadingly suggest the doc doesn't exist yet.
     sdd-micro has no Virtual Team, so none of this ever appears there.
 - **Documents** — every generated doc and its `Status:` (Draft/Approved/etc.), with a best-effort "what's next" guess, including the same persona ask shown on the Full Pipeline's Next box when the next doc has an owner. Each doc has a **View** button that reads the raw `.md` straight from disk into the page — no need to leave the browser to check content.
+- **Business Objectives** — chains `brd.md` §2 Business Objectives → §5's `Serves BO` column → `srd.md`'s Functional Requirements → `tasks.md`'s completion status, so each `BO-NNN` shows which `UC-NNN`s implement it and how much of that work is actually done (0% → Not Started, partial → In Progress, 100% → Done). Shown per-feature, plus a **cross-feature rollup card** above all the feature blocks — "of these business objectives across all features, which are met, which are pending, and where." Empty until `brd.md` §5 rows cite a `Serves BO`.
 - **Tasks** — parsed from `tasks.md` (works with both the full packs' checkbox-based tasks and sdd-micro's `**Status:**` field)
 - **Token Usage** — the running totals from `token-usage.md`, if token usage logging is enabled for that feature
 - **Jira Export** — the Epic/Story/Task links from the progressive export (`docs/jira/{feature}/keys.yml`), if you've run `/jira-push` or `sdd jira push`

{sddflow-2.7.74 → sddflow-2.7.82}/README.md

@@ -539,6 +539,7 @@ Shows, per feature under `.specify/features/`:
     BRD"), which would misleadingly suggest the doc doesn't exist yet.
     sdd-micro has no Virtual Team, so none of this ever appears there.
 - **Documents** — every generated doc and its `Status:` (Draft/Approved/etc.), with a best-effort "what's next" guess, including the same persona ask shown on the Full Pipeline's Next box when the next doc has an owner. Each doc has a **View** button that reads the raw `.md` straight from disk into the page — no need to leave the browser to check content.
+- **Business Objectives** — chains `brd.md` §2 Business Objectives → §5's `Serves BO` column → `srd.md`'s Functional Requirements → `tasks.md`'s completion status, so each `BO-NNN` shows which `UC-NNN`s implement it and how much of that work is actually done (0% → Not Started, partial → In Progress, 100% → Done). Shown per-feature, plus a **cross-feature rollup card** above all the feature blocks — "of these business objectives across all features, which are met, which are pending, and where." Empty until `brd.md` §5 rows cite a `Serves BO`.
 - **Tasks** — parsed from `tasks.md` (works with both the full packs' checkbox-based tasks and sdd-micro's `**Status:**` field)
 - **Token Usage** — the running totals from `token-usage.md`, if token usage logging is enabled for that feature
 - **Jira Export** — the Epic/Story/Task links from the progressive export (`docs/jira/{feature}/keys.yml`), if you've run `/jira-push` or `sdd jira push`

{sddflow-2.7.74 → sddflow-2.7.82}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sddflow"
-version = "2.7.74"
+version = "2.7.82"
 description = "SDD Framework CLI — initialize and upgrade Spec-Driven Development packs"
 readme = "README.md"
 requires-python = ">=3.9"

sddflow-2.7.82/sdd/__init__.py

@@ -0,0 +1 @@
+__version__ = "2.7.82"

{sddflow-2.7.74 → sddflow-2.7.82}/sdd/commands/confluence.py

@@ -10,7 +10,7 @@ from sdd.utils.confluence_client import ConfluenceClient
 from sdd.utils.md_to_cf import md_to_storage
 from sdd.utils.cf_to_md import cf_to_md
 from sdd.utils.manifest import read_manifest
-from sdd.utils.validate import resolve_doc_path, LIVING_SERVICE_DOCS
+from sdd.utils.validate import resolve_doc_path, LIVING_SERVICE_DOCS, PROJECT_SCOPED_DOCS
 
 console = Console()
 
@@ -63,11 +63,11 @@ def resolve_feature_parent_id(client: ConfluenceClient, cf_cfg, project_name: st
 
 def resolve_doc_parent_id(client: ConfluenceClient, cf_cfg, project_name: str,
                            feature_name: str, doc: str) -> str:
-    """Like resolve_feature_parent_id(), except living/service-level docs
-    (LIVING_SERVICE_DOCS) and "constitution" nest directly under the
-    Project page instead of a Feature page, since they're shared across
-    every feature, not per-feature."""
-    if doc in LIVING_SERVICE_DOCS or doc == "constitution":
+    """Like resolve_feature_parent_id(), except living/service-level docs,
+    "constitution", and "runbook" (PROJECT_SCOPED_DOCS) nest directly
+    under the Project page instead of a Feature page, since they're
+    shared across every feature, not per-feature."""
+    if doc in PROJECT_SCOPED_DOCS:
         return _ensure_container_page(client, cf_cfg.space_key, project_name, cf_cfg.parent_page_id)
     return resolve_feature_parent_id(client, cf_cfg, project_name, feature_name)
 
@@ -122,10 +122,11 @@ def _resolve_page_title(doc: str, project_name: str, feature: str,
                          page_map: dict) -> str:
     """Build the Confluence page title for a doc key.
 
-    Living/service-level docs (LIVING_SERVICE_DOCS) always resolve to ONE
-    page for the whole project — {feature} is stripped even if present in
-    the template, since these documents are shared across every feature,
-    never per-feature.
+    Living/service-level docs and "runbook" (PROJECT_SCOPED_DOCS, minus
+    "constitution" which is handled separately above) always resolve to
+    ONE page for the whole project — {feature} is stripped even if
+    present in the template, since these documents are shared across
+    every feature, never per-feature.
 
     Per-feature docs substitute {feature} into the title ONLY if the
     user's own page_map template contains that placeholder. This is
@@ -143,7 +144,7 @@ def _resolve_page_title(doc: str, project_name: str, feature: str,
         return _CONSTITUTION_PAGE_TITLE.replace("{project}", project_name)
     template = page_map.get(doc, f"{{project}} — {doc.upper()}")
     title = template.replace("{project}", project_name)
-    if doc in LIVING_SERVICE_DOCS:
+    if doc in LIVING_SERVICE_DOCS or doc == "runbook":
         title = title.replace(" — {feature}", "").replace("{feature}", "")
         return title.strip().rstrip("—").strip()
     return title.replace("{feature}", feature)

{sddflow-2.7.74 → sddflow-2.7.82}/sdd/commands/dashboard.py

@@ -350,6 +350,44 @@ function renderTasks(tasks) {
   `;
 }
 
+function renderBusinessObjectives(bos, opts) {
+  opts = opts || {};
+  if (!bos || bos.length === 0) {
+    return '<div class="empty">No BO-NNN rows in brd.md yet, or its Business Requirements section doesn’t cite a Serves BO column.</div>';
+  }
+  const rows = bos.map(bo => {
+    const ucCell = (bo.uc_ids && bo.uc_ids.length) ? escapeHtml(bo.uc_ids.join(', ')) : '<span class="sub">none linked</span>';
+    const progressCell = bo.task_count
+      ? `${bo.percent_done}% <span class="sub">(${bo.tasks_done}/${bo.task_count})</span>`
+      : '<span class="sub">no tasks linked</span>';
+    const featureCell = opts.showFeature
+      ? `<td><a href="#${featureAnchorId(bo.feature)}">${escapeHtml(bo.feature)}</a></td>`
+      : '';
+    return `
+      <tr>
+        <td>${bo.bo_id}</td>
+        <td>${escapeHtml(bo.objective)}${bo.metric ? `<div class="sub">${escapeHtml(bo.metric)}</div>` : ''}</td>
+        ${featureCell}
+        <td>${ucCell}</td>
+        <td>${badge(bo.status, 'task')}</td>
+        <td>${progressCell}</td>
+      </tr>`;
+  }).join('');
+  const featureHeader = opts.showFeature ? '<th>Feature</th>' : '';
+  return `
+    <table><thead><tr><th>BO</th><th>Objective</th>${featureHeader}<th>Use Cases</th><th>Status</th><th>Progress</th></tr></thead><tbody>${rows}</tbody></table>`;
+}
+
+function renderBusinessObjectivesOverview(businessObjectives) {
+  if (!businessObjectives || businessObjectives.length === 0) return '';
+  return `
+    <div class="card card-wide" style="margin-bottom:1.5rem">
+      <h2>Business Objectives</h2>
+      <div class="sub" style="margin-bottom:.5rem">Rolled up from each feature's brd.md (§2 Business Objectives → §5 Serves BO) through srd.md and tasks.md — which use cases implement each objective, and how much of that work is done.</div>
+      ${renderBusinessObjectives(businessObjectives, {showFeature: true})}
+    </div>`;
+}
+
 function linkPill(kind, link) {
   if (!link) return '';
   if (link.error) return `<span class="pill pill-bad" title="${escapeHtml(link.error)}">${kind} ⚠</span>`;
@@ -673,6 +711,7 @@ function renderFeature(f, project) {
     <div class="grid feature-grid">
       <div class="card card-wide"><h2>Full Pipeline</h2>${renderPipelineFlow(f, project)}</div>
       <div class="card card-wide"><h2>Documents</h2>${renderDocs(f.docs, f.current_stage, f.name, local.confluence, local.jira_review)}</div>
+      <div class="card card-wide"><h2>Business Objectives</h2>${renderBusinessObjectives(f.business_objectives)}</div>
       <div class="card"><h2>Tasks</h2>${renderTasks(f.tasks)}</div>
       <div class="card"><h2>Token Usage</h2>${renderTokenUsage(f.token_usage)}</div>
       <div class="card"><h2>Jira Export</h2>${renderJiraExport(local.jira, exportEntry)}</div>
@@ -712,6 +751,7 @@ function render() {
   const data = lastData;
   document.getElementById('generated-at').textContent = 'Generated ' + data.generated_at;
   const overview = renderFeatureOverview(data.features);
+  const boOverview = renderBusinessObjectivesOverview(data.business_objectives);
   const features = data.features.length
     ? data.features.map(f => renderFeature(f, data.project)).join('')
     : '<div class="empty">No features under .specify/features/ yet — run <code>/specify</code> (or <code>sdd specify</code>) to create your first one.</div>';
@@ -737,7 +777,7 @@ function render() {
     };
   }
 
-  root.innerHTML = renderProject(data.project, data.constitution) + overview + features;
+  root.innerHTML = renderProject(data.project, data.constitution) + overview + boOverview + features;
 
   if (focus) {
     const selector = `.${focus.cls}[data-feature="${CSS.escape(focus.feature)}"][data-doc="${CSS.escape(focus.doc)}"]`;

{sddflow-2.7.74 → sddflow-2.7.82}/sdd/commands/review.py

@@ -14,7 +14,7 @@ from sdd.utils.confluence_client import ConfluenceClient
 from sdd.utils.md_to_cf import md_to_storage
 from sdd.utils.manifest import read_manifest
 from sdd.utils.status import persona_for
-from sdd.utils.validate import resolve_doc_path, LIVING_SERVICE_DOCS
+from sdd.utils.validate import resolve_doc_path, PROJECT_SCOPED_DOCS
 from sdd.utils.dashboard_comments import unacknowledged, acknowledge
 
 console = Console()
@@ -52,10 +52,10 @@ def _is_locally_approved(doc: str) -> bool:
 def _doc_md_path(doc: str, feature: str | None) -> Path | None:
     """Resolve the on-disk path for a doc key, or None if unresolvable.
 
-    "constitution" and living/service-level docs (data-model,
+    "constitution", "runbook", and living/service-level docs (data-model,
     security-design, api-spec) resolve to a fixed path regardless of
     feature. Everything else resolves to .specify/features/{feature}/{doc}.md."""
-    if doc == "constitution" or doc in LIVING_SERVICE_DOCS:
+    if doc in PROJECT_SCOPED_DOCS:
         return resolve_doc_path(doc, "")
     manifest     = read_manifest() or {}
     proj         = manifest.get("project") or {}

{sddflow-2.7.74 → sddflow-2.7.82}/sdd/commands/upgrade.py

@@ -2880,6 +2880,346 @@ MIGRATIONS = [
         ],
         "migrate": lambda m: {**m, "sdd_version": "2.7.74"},
     },
+    {
+        "from":        "2.7.74",
+        "to":          "2.7.75",
+        "description": "Fix: sdd_parser.py never matched the actual shipped stories.md/tasks.md templates -- sdd jira push and sdd pr create --task silently found zero stories/tasks for every real generated feature",
+        "notes": [
+            "Found while helping a user debug why 'sdd jira push' created "
+            "nothing even after fixing Jira/Confluence credentials -- "
+            "traced it to sdd_parser.py's regexes expecting a heading/"
+            "field format ('### STORY-NNN — Title' em-dash, "
+            "'**As a**'/'**Satisfies:**' bold fields, '## TASK-NNN' H2) "
+            "that the shipped feature-story-template.md/tasks-template.md "
+            "have not used for some time (they use '### STORY-NNN: "
+            "Title' colon, '**As**'/'**Linked FRs:**' for stories, and "
+            "'### TASK-NNN' H3 with entirely plain/unbolded fields for "
+            "tasks) -- parse_stories()/parse_tasks() returned an empty "
+            "list for every correctly-generated document",
+            "This silently broke 'sdd jira push --level story/task' "
+            "(reported 'No stories or tasks found') and 'sdd pr create "
+            "--task TASK-NNN' (reported 'TASK-NNN not found in "
+            "tasks.md') for every project using the current templates "
+            "-- both are on the framework's golden path",
+            "sdd_parser.py rewritten to match the current templates "
+            "while still accepting the older em-dash/bold-field style "
+            "found in this repo's own worked examples, so already-"
+            "generated docs in either style parse correctly",
+            "Also fixed: _normalize_moscow() required an exact 'must "
+            "have' string match, but the shipped template's bucket "
+            "headers are 'Must Have Stories' (trailing word) -- every "
+            "story silently fell through to the could-have default, "
+            "mapping every Jira Story to Low priority regardless of "
+            "its actual MoSCoW bucket",
+            "New golden-template tests parse the actual shipped "
+            "feature-story-template.md/tasks-template.md files directly "
+            "(not just hand-written fixtures) so a future template edit "
+            "that breaks the parser fails CI instead of shipping silently "
+            "broken again",
+            "This migration only bumps sdd_version -- no manifest.yml "
+            "field changes for any pack",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.75"},
+    },
+    {
+        "from":        "2.7.75",
+        "to":          "2.7.76",
+        "description": "Fix: /release and /implement's runbook never went through Jira/Confluence review despite document_reviews.runbook/.release being fully documented and configurable",
+        "notes": [
+            "Prompted by a user asking for a full audit of every pipeline "
+            "step's Jira/Confluence coverage, after the sdd_parser.py fix "
+            "above -- release.prompt.md had ZERO Jira/Confluence wiring "
+            "for release.md (only an informal chat sign-off), and "
+            "implement.prompt.md never submitted the runbook "
+            "(docs/runbook/local-setup.md) for review at all -- not even "
+            "chat-mode approval -- despite CLAUDE.md's own Jira-mode "
+            "sequence table documenting 'release phase: Runbook -> "
+            "Release, reviewer: DevOps -> Release Manager' and the "
+            "shipped integrations.yml.example already configuring both "
+            "document_reviews.runbook and .release with sequence numbers",
+            "Backend bug found in the same sweep: resolve_doc_path() had "
+            "no case for 'runbook' -- 'sdd review submit --doc runbook' "
+            "would have resolved to the nonexistent "
+            ".specify/features/{feature}/runbook.md instead of the real "
+            "docs/runbook/local-setup.md, and confluence.py's page-"
+            "nesting/title logic didn't treat 'runbook' as project-"
+            "scoped (living) the way data-model/security-design/api-spec/"
+            "constitution already are -- new PROJECT_SCOPED_DOCS constant "
+            "in validate.py fixes both",
+            "release.prompt.md and implement.prompt.md now submit "
+            "release.md/runbook.md through the same Submit-for-Review + "
+            "review-decision-step flow every other document uses, across "
+            "all 5 packs",
+            "integrations.yml.example's page_map.release entry was also "
+            "commented out by default even though document_reviews.release "
+            "was already active -- a user copying the example as-is would "
+            "have hit a missing-page_map-entry error the first time this "
+            "new wiring ran; uncommented to match runbook's existing "
+            "active entry",
+            "This migration only bumps sdd_version -- no manifest.yml "
+            "field changes for any pack",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.76"},
+    },
+    {
+        "from":        "2.7.76",
+        "to":          "2.7.77",
+        "description": "Fix: self-approval risk undocumented, coverage gate was a bare echo, no test caught either -- verified all three with grep before fixing, per external review of the sdd_parser.py/release.md audit",
+        "notes": [
+            "An external agent reviewed the two prior fixes (sdd_parser.py, "
+            "release.md/runbook wiring) and raised several concerns. "
+            "Re-checked every claim with grep/read against the actual "
+            "repo instead of accepting either the review's or this "
+            "agent's own prior assessment on faith -- some held up, some "
+            "didn't (e.g. the review's '245 tests' figure was stale; "
+            "actual count was 592 at the time). Three confirmed, real "
+            "gaps were fixed",
+            "review-gates.md now explicitly states the self-approval "
+            "risk in chat mode: nothing stops the same conversation that "
+            "drafted a document from also being the one that approves "
+            "it -- no independent reviewer identity check exists. This "
+            "was previously only implicit in the scope-based mode "
+            "guidance",
+            "quality-gate.yml's 'Enforce coverage gate' step was a bare "
+            "`echo` in every pack (confirmed by reading the actual "
+            "workflow file) -- it always printed a success-sounding "
+            "message regardless of whether coverage was configured at "
+            "all. Replaced with a real tripwire: the step now greps "
+            "pom.xml for jacoco-maven-plugin's <rules> block (Java packs) "
+            "or vitest/jest config for coverageThreshold/thresholds (Node "
+            "packs), and fails the CI job with actionable guidance if "
+            "the configuration is missing -- across all 5 packs, "
+            "including fullstack's separate backend+frontend jobs",
+            "New test_prompt_review_coverage.py: for every doc key with "
+            "an active document_reviews entry in the shipped "
+            "integrations.yml.example, asserts the owning .prompt.md "
+            "file actually contains a 'sdd review submit --doc {key}' "
+            "call, across all 5 packs (56 cases). This is the cheap, "
+            "buildable version of 'run the pipeline against a mocked "
+            "Jira/Confluence' -- prompts are AI instructions, not "
+            "executable code, so a structural presence check is what's "
+            "actually feasible in CI. Verified by temporarily reverting "
+            "release.prompt.md to its pre-fix state and confirming the "
+            "new test fails exactly where the real bug was, then passes "
+            "again once restored",
+            "This migration only bumps sdd_version -- no manifest.yml "
+            "field changes for any pack",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.77"},
+    },
+    {
+        "from":        "2.7.77",
+        "to":          "2.7.78",
+        "description": "Fix: sdd-universal missing UI templates, brd-template.md drift, design-template.md numbering gap -- template quality review found real gaps beyond docs/CI",
+        "notes": [
+            "sdd-universal was missing ux-flow-template.md, "
+            "screen-spec-template.md, component-spec-template.md, and "
+            "component-library-template.md even though its own "
+            "specify-doc.prompt.md documents /specify-doc "
+            "component-spec|ux-flow|screen-spec as valid commands and "
+            "reads .specify/templates/{doc}-template.md directly -- a "
+            "broken reference for exactly the mobile/frontend project "
+            "types sdd-universal auto-detects. Added all four",
+            "ux-flow-template.md, screen-spec-template.md, and "
+            "component-spec-template.md had no ID scheme or Version "
+            "History table, unlike every other template in the system. "
+            "Added FLOW/ERR/EDGE-NNN, SCR-NNN, and COMP-NNN respectively, "
+            "plus Version History to all three. Enrolled into "
+            "_shared/full/ since they were already byte-identical across "
+            "every pack that ships them",
+            "brd-template.md had drifted uncoordinated: sdd-universal's "
+            "copy had a Section 9 Investment Summary and domain-aware "
+            "regulation pre-seeding (PCI/HIPAA/GDPR) the other four packs "
+            "(byte-identical to each other) never received. Unlike "
+            "api-spec/data-model/security-design/runbook -- which "
+            "legitimately vary by project type -- BRD content has no "
+            "such reason to differ. Enrolled into _shared/full/ using "
+            "sdd-universal's fuller version as canonical",
+            "design-template.md Section 3 skipped from 3.2 to 3.5 with "
+            "no 3.3/3.4 content anywhere in the file -- renumbered to "
+            "3.3",
+            "Known gaps NOT fixed in this pass: sdd-universal's "
+            "specify-doc.prompt.md has no project-type branching for "
+            "which flavor of data-model/security-design template to use "
+            "(a detected frontend/mobile project would get the "
+            "DB-schema/server-side flavor); sdd-universal's api-spec, "
+            "data-model, runbook, and openapi templates are each missing "
+            "content sdd-backend-service's same-flavor copies already "
+            "have; security-design-template.md has a structural (not "
+            "content) mismatch between backend and universal",
+            "This migration only bumps sdd_version -- no manifest.yml "
+            "field changes for any pack",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.78"},
+    },
+    {
+        "from":        "2.7.78",
+        "to":          "2.7.79",
+        "description": "Fix: runbook-template.md missing living-doc framing in 4 packs, security-design/data-model/api-spec inconsistencies across packs, release-template.md pilot-scope broken rollback reference, sdd-universal had no project-type flavor branching for data-model/security/runbook",
+        "notes": [
+            "runbook-template.md was missing its 'Living artifact' framing "
+            "paragraph and used '# Feature: {Feature Name}' instead of "
+            "'# Service:'/'# App:' in frontend-spa, mobile, fullstack, and "
+            "sdd-universal (only sdd-backend-service had it correct) -- an "
+            "agent following the template literally would treat the "
+            "runbook as a fresh per-feature doc instead of extending the "
+            "living one, silently dropping a prior feature's additions. "
+            "Fixed all four",
+            "security-design-template.md was inconsistent across packs: "
+            "only sdd-backend-service had a Version History table; only "
+            "sdd-universal had the CVSS scoring column and the 2-row "
+            "Security Officer/Tech Lead Approvals table. Reconciled all "
+            "five packs to have all three",
+            "data-model-template.md and api-spec-template.md were missing "
+            "Version History tables in sdd-universal (both docs) and "
+            "sdd-fullstack (api-spec only). Added. Also fixed "
+            "sdd-universal's api-spec-template.md References row, which "
+            "cited 'arch.summary.md ... ports/adapters' -- leftover text "
+            "that didn't match how api-spec.md is actually fed (per "
+            "plan-design.prompt.md Section 3: design.summary.md, which "
+            "feature added/changed which endpoints)",
+            "release-template.md Section 7 Rollback Plan pointed to "
+            "docs/runbook/local-setup.md in sdd-backend-service, "
+            "frontend-spa, mobile, and fullstack even at pilot scope, "
+            "where the runbook is never generated -- a broken reference. "
+            "Backported sdd-universal's pilot-scope fallback rollback "
+            "table (already correct there) to all four packs, plus two "
+            "extra Post-Deploy Smoke Test monitoring rows sdd-universal "
+            "already had",
+            "sdd-universal's specify-doc.prompt.md read one single "
+            "template flavor for data-model and security-design "
+            "regardless of detected project_type -- a frontend-spa or "
+            "mobile project would get the DB-schema/server-side flavor "
+            "instead of state/storage-model or local-cache-model content. "
+            "Added project_type branching (frontend-spa/desktop -> "
+            "*-template-frontend.md, mobile -> *-template-mobile.md, "
+            "else -> default) to the shared specify-doc.prompt.md source "
+            "(safe no-op for the other four packs, which have no "
+            "project_type field) and shipped the new frontend/mobile "
+            "flavor template files for sdd-universal. Same fix applied to "
+            "runbook generation in implement.prompt.md",
+            "Verified: sync-blocks.sh clean, cli-python pytest 648/648, "
+            "assert-output.sh 33/33 on both worked examples, setup smoke "
+            "tests 15/15",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.79"},
+    },
+    {
+        "from":        "2.7.79",
+        "to":          "2.7.80",
+        "description": "Fix: data-model-template.md missing Version History in frontend-spa/mobile/fullstack, security-design-template.md STRIDE column wording inconsistency in sdd-universal -- found while verifying the v2.7.79 fix batch's own consistency",
+        "notes": [
+            "data-model-template.md was missing '## Version History' in "
+            "sdd-frontend-spa, sdd-mobile, and sdd-fullstack -- only "
+            "sdd-backend-service and (as of 2.7.79) sdd-universal had it. "
+            "Found because sdd-universal's new data-model-template-frontend.md/"
+            "-mobile.md flavor files (copied verbatim from those packs' own "
+            "templates) diffed non-empty against their source -- the "
+            "source packs were the ones missing content, not the copies. "
+            "Added Version History to all three",
+            "security-design-template.md's STRIDE threat table column was "
+            "'Threat (STRIDE)' in sdd-universal but 'Threat (STRIDE "
+            "category)' in the other four packs -- pre-existing wording "
+            "drift, not something the 2.7.79 CVSS-column fix introduced. "
+            "Normalized sdd-universal to match",
+            "Verified: sync-blocks.sh clean, cli-python pytest 648/648, "
+            "assert-output.sh 33/33",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.80"},
+    },
+    {
+        "from":        "2.7.80",
+        "to":          "2.7.81",
+        "description": "Fix: sdd-micro/setup.sh had zero test coverage -- test-setup.sh only ever tested sdd-universal's setup.sh (hardcoded PACK_DIR); no manifest.yml field changes for any pack, including sdd-micro (this is a CI/test-harness fix, not a pack-content change)",
+        "notes": [
+            "Found while reviewing sdd-micro end-to-end: "
+            "packs/_shared/tests/test-setup.sh's own header says 'Smoke "
+            "tests for sdd-universal/setup.sh' and hardcodes "
+            "PACK_DIR=packs/sdd-universal -- sdd-micro/setup.sh (a "
+            "materially different script: --project/--feature only, no "
+            "--type/--scope, its own non-interactive default fallback to "
+            "'untitled-project'/'main') was never exercised by CI despite "
+            "root CLAUDE.md describing the smoke-test suite as covering "
+            "'injection-class names, all project types, and "
+            "non-interactive execution' in a way that read as a blanket "
+            "guarantee",
+            "Added packs/_shared/tests/test-setup-micro.sh, mirroring "
+            "test-setup.sh's ok()/nok() structure and covering the same "
+            "injection classes (quotes, backslash, ampersand, slash, "
+            "unicode) plus two cases specific to this script: the "
+            "no-args non-interactive default path, and the 'unknown "
+            "option' rejection (sdd-micro's setup.sh has no --type flag, "
+            "unlike sdd-universal's)",
+            "Wired into .github/workflows/ci.yml's existing "
+            "setup-smoke-tests job as a second step, and documented in "
+            "root CLAUDE.md's Testing Setup Scripts section",
+            "Verified the new test actually has teeth: temporarily "
+            "disabled sdd-micro/setup.sh's double-quote validation guard, "
+            "confirmed the 2 double-quote-rejection cases failed as "
+            "expected (exit 1), then restored the original file (git "
+            "diff clean) and re-ran clean (12/12)",
+            "Deliberately kept sdd-micro's own manifest.yml sdd_version "
+            "untouched (still 2.7.41) -- this fix only adds test/CI "
+            "infrastructure in this repo, it does not change any file "
+            "sdd-micro itself ships to a user's project via `sdd init "
+            "--pack sdd-micro`",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.81"},
+    },
+    {
+        "from":        "2.7.81",
+        "to":          "2.7.82",
+        "description": "Feature: Business Objectives traceability + dashboard rollup -- brd.md's Business Objectives (§2) and Business Requirements (§5) were previously unlinked siblings; adds a 'Serves BO' column to §5 and rolls BO -> BR -> FR -> TASK up into a per-feature and cross-feature Business Objectives view in `sdd dashboard`",
+        "notes": [
+            "Added 'Serves BO' column to brd-template.md's §5 Business "
+            "Requirements table (all 5 non-micro packs) -- every BR-NNN "
+            "must now cite which BO-NNN from §2 it serves. Updated "
+            "specify-brd.prompt.md with fill instructions",
+            "Added status.py parsers: _parse_brd_bo (brd.md §2/§5, "
+            "tolerant of 3- or 4-column Business Objectives tables and "
+            "legacy 'Satisfies' column headers), _parse_uc_traces "
+            "(use-cases.md Use Case Index table, falls back to scanning "
+            "narrative '### UC-NNN' sections' '**Trace:**'/'**BR "
+            "Traces:**' lines when no Index table exists), _parse_srd_fr "
+            "(srd.md Functional Requirements table, tolerant of the "
+            "5-column canonical shape and a 4-column 'Satisfies' "
+            "variant, plus §4 Use Case Coverage as a UC-link fallback)",
+            "Added build_bo_rollup(): chains BO -> BR (brd.md 'Serves "
+            "BO') -> FR (srd.md 'Source'/'Satisfies', the reliable "
+            "bridge since use-cases.md's FR Traces column is only "
+            "backfilled by a manual /specify-srd re-run and is often "
+            "skipped in practice) -> TASK (tasks.md 'Satisfies:' field + "
+            "completion status). UC-NNN is gathered from both "
+            "use-cases.md and srd.md for display, but status/percent-done "
+            "is computed from the BR->FR->TASK bridge only",
+            "Wired into build_feature_status() (per-feature "
+            "'business_objectives' key) and build_project_status() (flat "
+            "cross-feature 'business_objectives' list, each row tagged "
+            "with its feature name -- BO-NNN numbering is local to each "
+            "feature's brd.md, same as the existing Actor Registry "
+            "pattern)",
+            "Added a 'Business Objectives' card to `sdd dashboard`: a "
+            "cross-feature rollup card (BO, Objective, Feature, Use "
+            "Cases, Status, Progress) shown above the per-feature blocks, "
+            "plus a per-feature card in each feature's block",
+            "Status computed by task completion percentage (0 done -> "
+            "Not Started, some done or in-progress -> In Progress, all "
+            "done -> Done), not release.md's BO closure field -- picked "
+            "so the dashboard reflects live task state rather than a "
+            "field only updated at /release time",
+            "Verified end-to-end against examples/todo-api's real "
+            "brd.md/use-cases.md/srd.md/tasks.md (which deviate from the "
+            "raw templates in exactly the ways the tolerant parsing "
+            "above accounts for) via the dashboard's live HTTP server, "
+            "screenshotted in both light and dark mode",
+            "Added 20 pytest cases covering 3-vs-4-column BO tables, "
+            "legacy 'Satisfies' headers, unfilled template placeholders, "
+            "the Use Case Index fallback, orphaned BRs, and the flattened "
+            "cross-feature rollup",
+            "Verified: sync-blocks.sh clean, cli-python pytest 664/664",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.82"},
+    },
 ]