sddflow 2.7.58__tar.gz → 2.7.59__tar.gz

{sddflow-2.7.58 → sddflow-2.7.59}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sddflow
-Version: 2.7.58
+Version: 2.7.59
 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

{sddflow-2.7.58 → sddflow-2.7.59}/pyproject.toml

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

sddflow-2.7.59/sdd/__init__.py

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

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/commands/dashboard.py

@@ -682,7 +682,7 @@ def _fetch_review_links(feature: str) -> dict:
             try:
                 issue = jira_client.find_by_label(cfg.jira.key_for("review"), f"sdd-doc:{feature}:{doc_key}")
                 if issue:
-                    review_status, comments = _get_review_status(
+                    review_status, comments, _ = _get_review_status(
                         doc_key, jira_client, cfg.jira.key_for("review"), cfg, feature,
                     )
                     entry["jira"] = {

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/commands/review.py

@@ -115,13 +115,40 @@ def _mark_md_approved(md_path: Path) -> bool:
     return True
 
 
-def _push_doc_page(doc: str, md_path: Path, feature_name: str) -> str | None:
-    """Upsert the document's Confluence page so it reflects the approved .md.
+def _jira_status_banner(issue_key: str, issue_url: str, status: str, role: str) -> str:
+    """Confluence storage-format panel summarizing the Jira review ticket's
+    link and current status, prepended to the page body on every push so a
+    reviewer can see review state without leaving Confluence."""
+    macro_type = {"APPROVED": "success", "NEEDS_REVISION": "warning"}.get(status, "info")
+    label = {
+        "APPROVED":       "Approved",
+        "NEEDS_REVISION": "Needs Revision",
+        "PENDING":        "Pending review",
+    }.get(status, status)
+    return (
+        f'<ac:structured-macro ac:name="{macro_type}">'
+        f'<ac:rich-text-body><p>'
+        f'<strong>Jira review:</strong> '
+        f'<a href="{issue_url}">{issue_key}</a> — <strong>{label}</strong>'
+        f' (assigned: {role})'
+        f'</p></ac:rich-text-body>'
+        f'</ac:structured-macro>'
+    )
+
+
+def _push_doc_page(doc: str, md_path: Path, feature_name: str) -> tuple[str, str] | None:
+    """Upsert the document's Confluence page so it reflects the current .md.
 
-    Returns the page title on success, or None when Confluence is not
-    configured. Raises on push errors — callers decide how fatal that is.
-    Page title resolution matches `sdd review submit`: document_reviews entry
-    first, then the confluence page_map, then a sensible default."""
+    Returns (page_title, page_url) on success, or None when Confluence is
+    not configured. Raises on push errors — callers decide how fatal that
+    is. Page title resolution matches `sdd review submit`: document_reviews
+    entry first, then the confluence page_map, then a sensible default.
+
+    When a Jira review ticket already exists for this doc (jira: configured
+    and document_reviews has an entry for it), a status banner linking to
+    that ticket is prepended to the page body -- this is what lets a
+    reviewer see the Jira link + current status directly on Confluence
+    instead of having to check Jira separately."""
     try:
         cfg = load_integrations()
     except FileNotFoundError:
@@ -147,16 +174,33 @@ def _push_doc_page(doc: str, md_path: Path, feature_name: str) -> str | None:
     prof      = load_profile(cfg.profile)
     session   = build_session(prof)
     cf_client = ConfluenceClient(session, prof.base_url)
+
+    banner = ""
+    if cfg.jira and doc in cfg.document_reviews:
+        try:
+            jira_client = JiraClient(session, prof.base_url)
+            status, _, issue = _get_review_status(
+                doc, jira_client, cfg.jira.key_for("review"), cfg, feature_name,
+            )
+            if issue:
+                issue_url = f"{prof.base_url}/browse/{issue['key']}"
+                banner = _jira_status_banner(
+                    issue["key"], issue_url, status, cfg.document_reviews[doc].reviewer_role,
+                )
+        except Exception:
+            pass  # banner is a best-effort addition -- never blocks the page push itself
+
     body_html, attachments, diagram_warnings = md_to_storage(md_path.read_text(), cfg.confluence.diagrams)
     from sdd.commands.confluence import resolve_doc_parent_id, upload_diagram_attachments
     parent_id = resolve_doc_parent_id(cf_client, cfg.confluence, project_name, feature_name, doc)
     page, _created = cf_client.upsert_page(
-        cfg.confluence.space_key, title, body_html, parent_id,
+        cfg.confluence.space_key, title, banner + body_html, parent_id,
     )
     upload_diagram_attachments(cf_client, page["id"], attachments)
     for w in diagram_warnings:
         console.print(f"  [yellow]!  {w}[/yellow]")
-    return title
+    page_url = f"{prof.base_url}/wiki{page.get('_links', {}).get('webui', '')}"
+    return title, page_url
 
 
 # ── Text extraction ────────────────────────────────────────────────────────────
@@ -231,29 +275,32 @@ def _get_review_status(
     project_key: str,
     cfg: IntegrationsConfig,
     feature_name: str,
-) -> tuple[str, list[dict]]:
-    """Return (status, comments).
+) -> tuple[str, list[dict], dict | None]:
+    """Return (status, comments, issue).
     status: APPROVED | NEEDS_REVISION | PENDING | NOT_SUBMITTED
+    issue is the raw Jira issue dict (or None if never submitted) -- callers
+    that also need the issue key/link (e.g. the Confluence status banner)
+    reuse this instead of a second find_by_label lookup.
 
     Label is feature-qualified — must match the label `review_submit` writes,
     or a submitted review would never be found again.
     """
     issue = client.find_by_label(project_key, f"sdd-doc:{feature_name}:{doc_key}")
     if not issue:
-        return "NOT_SUBMITTED", []
+        return "NOT_SUBMITTED", [], None
 
     jira_status = issue.get("fields", {}).get("status", {}).get("name", "")
     comments    = client.get_comments(issue["key"])
 
     if jira_status in cfg.approved_statuses:
-        return "APPROVED", comments
+        return "APPROVED", comments, issue
 
     for c in comments:
         text = _extract_text(c.get("body", "")).lower()
         if any(kw in text for kw in cfg.approved_keywords):
-            return "APPROVED", comments
+            return "APPROVED", comments, issue
 
-    return ("NEEDS_REVISION" if comments else "PENDING"), comments
+    return ("NEEDS_REVISION" if comments else "PENDING"), comments, issue
 
 
 def _check_predecessor(
@@ -275,7 +322,7 @@ def _check_predecessor(
     if not preds:
         return True, None
     pred_key = preds[0]
-    status, _ = _get_review_status(pred_key, client, cfg.jira.key_for("review"), cfg, feature_name)
+    status, _, _ = _get_review_status(pred_key, client, cfg.jira.key_for("review"), cfg, feature_name)
     return (status == "APPROVED"), (None if status == "APPROVED" else pred_key)
 
 
@@ -688,6 +735,16 @@ def review_submit(doc, profile, feature):
 
     _record_review_link(doc, story_key)
 
+    # ── Re-push Confluence with the now-existing Jira link/status banner ──────
+    # The first push above (before the ticket existed) couldn't include this --
+    # _push_doc_page's own find-by-label lookup will now find the ticket just
+    # created/updated and prepend a banner showing its link + live status, so
+    # a reviewer sees Jira state without leaving Confluence.
+    try:
+        _push_doc_page(doc, md_path, feature_name)
+    except Exception as e:
+        console.print(f"  [yellow]!  Could not stamp Jira status onto Confluence: {e}[/yellow]")
+
     if epic_key:
         _link_review_story_to_epic(jira_client, story_key, epic_key, cfg.jira)
 
@@ -774,7 +831,9 @@ def review_push_questions(doc, profile, feature):
     page_title = None
     if cfg.confluence:
         try:
-            page_title = _push_doc_page(doc, md_path, feature_name)
+            pushed = _push_doc_page(doc, md_path, feature_name)
+            if pushed:
+                page_title, _page_url = pushed
         except Exception as e:
             console.print(f"  [yellow]!  Confluence push failed: {e}[/yellow]")
 
@@ -973,8 +1032,9 @@ def review_pull_answers(doc, profile, feature):
         if cfg.confluence:
             for doc_key, loc_path in patched_paths.items():
                 try:
-                    title = _push_doc_page(doc_key, loc_path, feature_name)
-                    if title:
+                    pushed = _push_doc_page(doc_key, loc_path, feature_name)
+                    if pushed:
+                        title, _page_url = pushed
                         console.print(f"  [green]✓[/green]  Confluence page refreshed: [cyan]{title}[/cyan]")
                 except Exception as e:
                     console.print(f"  [yellow]!  Could not refresh Confluence page for {doc_key}: {e}[/yellow]")
@@ -1030,10 +1090,22 @@ def review_check(doc, profile, feature):
         raise SystemExit(3)
 
     client  = JiraClient(session, prof.base_url)
-    status, comments = _get_review_status(doc, client, cfg.jira.key_for("review"), cfg, feature_name)
+    status, comments, _ = _get_review_status(doc, client, cfg.jira.key_for("review"), cfg, feature_name)
     doc_cfg = cfg.document_reviews.get(doc)
     role    = doc_cfg.reviewer_role if doc_cfg else "reviewer"
 
+    # ── Refresh the Confluence status banner to match what we just polled ─────
+    # Best-effort: a reviewer who only looks at Confluence (never Jira
+    # directly) should see the same status this command just printed, without
+    # having to wait for the next `sdd review submit`/`apply`/`approve`.
+    if cfg.confluence:
+        try:
+            md_path = resolve_doc_path(doc, feature_name)
+            if md_path.exists():
+                _push_doc_page(doc, md_path, feature_name)
+        except Exception:
+            pass
+
     if status == "APPROVED":
         console.print(f"  [green]✓  {doc.upper()} — APPROVED[/green]")
         console.print()
@@ -1164,8 +1236,9 @@ def review_approve(doc, local, by, note, feature, no_confluence):
             try:
                 manifest     = read_manifest() or {}
                 feature_name = feature or (manifest.get("project") or {}).get("feature", "")
-                title = _push_doc_page(doc, md_path, feature_name)
-                if title:
+                pushed = _push_doc_page(doc, md_path, feature_name)
+                if pushed:
+                    title, _page_url = pushed
                     console.print(f"  [green]✓[/green]  Confluence page updated: [cyan]{title}[/cyan]")
                 else:
                     console.print("  [dim]·  Confluence not configured — page not updated[/dim]")
@@ -1234,31 +1307,21 @@ def review_apply(doc, profile, feature):
         console.print(f"  [red]✗  '{doc}' not found in document_reviews[/red]")
         raise SystemExit(1)
 
-    project_name = proj.get("name", "Project")
-
     jira_client = JiraClient(session, prof.base_url)
-    cf_client   = ConfluenceClient(session, prof.base_url)
 
-    # Re-push updated doc
+    # Re-push updated doc (picks up the Jira link/status banner automatically,
+    # since the review ticket from the original `sdd review submit` already exists)
     try:
         md_path = resolve_doc_path(doc, feature_name)
     except ValueError as e:
         console.print(f"  [red]✗  {e}[/red]")
         raise SystemExit(1)
-    page_url     = ""
+    page_url = ""
     if md_path.exists():
-        page_title = doc_cfg.confluence_page.replace("{project}", project_name).replace("{feature}", feature_name)
-        body_html, attachments, diagram_warnings = md_to_storage(md_path.read_text(), cfg.confluence.diagrams)
-        from sdd.commands.confluence import resolve_doc_parent_id, upload_diagram_attachments
-        parent_id = resolve_doc_parent_id(cf_client, cfg.confluence, project_name, feature_name, doc)
-        page, _    = cf_client.upsert_page(
-            cfg.confluence.space_key, page_title, body_html, parent_id,
-        )
-        upload_diagram_attachments(cf_client, page["id"], attachments)
-        page_url = f"{prof.base_url}/wiki{page.get('_links', {}).get('webui', '')}"
-        console.print(f"  [green]✓[/green]  Confluence updated: [cyan]{page_title}[/cyan]")
-        for w in diagram_warnings:
-            console.print(f"  [yellow]!  {w}[/yellow]")
+        pushed = _push_doc_page(doc, md_path, feature_name)
+        if pushed:
+            page_title, page_url = pushed
+            console.print(f"  [green]✓[/green]  Confluence updated: [cyan]{page_title}[/cyan]")
     else:
         console.print(f"  [dim]·[/dim]  {md_path} not found — skipping Confluence update")
 
@@ -1338,7 +1401,7 @@ def review_status(profile, feature):
                 icon, label, style = "🔒", "Blocked", "dim"
                 all_statuses[key] = "BLOCKED"
             else:
-                st, _ = _get_review_status(key, client, cfg.jira.key_for("review"), cfg, feature_name)
+                st, _, _ = _get_review_status(key, client, cfg.jira.key_for("review"), cfg, feature_name)
                 all_statuses[key] = st
                 if st == "APPROVED":
                     icon, label, style = "✓ ", "Approved",       "green"

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/commands/upgrade.py

@@ -2306,6 +2306,42 @@ MIGRATIONS = [
         ],
         "migrate": lambda m: {**m, "sdd_version": "2.7.58"},
     },
+    {
+        "from":        "2.7.58",
+        "to":          "2.7.59",
+        "description": "Feature: Confluence pages for documents under Jira review now show a live Jira link + status banner, and page_map covers every generated doc type (qa-testcases, tasks, checklist, and the living/service docs) -- no manifest schema changes",
+        "notes": [
+            "User asked why a doc pushed to Jira for review didn't also "
+            "get its Confluence page stamped with the ticket link/status "
+            "so a reviewer could see it without leaving Confluence -- the "
+            "page only ever mirrored the .md content, never the Jira "
+            "state, since the two pushes happened in unrelated code paths",
+            "sdd review submit/check/apply now prepend a small info/"
+            "success/warning panel (via the new _push_doc_page banner) "
+            "showing the ticket key, link, and live status (Pending/"
+            "Needs Revision/Approved) -- refreshed every time the CLI "
+            "touches that document's review state, so it never goes "
+            "stale between submit and the reviewer's eventual decision",
+            "Only applies to doc keys with a document_reviews entry (i.e. "
+            "actually under Jira review) -- docs pushed via the page_map "
+            "fallback alone (no Jira gate configured) get a plain page, "
+            "same as before",
+            "User also asked for a Confluence page for 'QA test case etc "
+            "-- whatever there in local md file' -- page_map in "
+            "integrations.yml.example now also covers qa-testcases, "
+            "tasks, checklist, and the 4 living/service-level docs "
+            "(data-model, security-design, api-spec, component-library), "
+            "so `sdd confluence push --doc <key>` works for all of them, "
+            "not just the phase-gated documents",
+            "6 new tests: banner HTML per status, submit stamps a Pending "
+            "banner once the ticket exists, check refreshes an existing "
+            "page to Approved, and the page_map fallback path (no Jira "
+            "gate) omits the banner entirely",
+            "This migration only bumps sdd_version -- no manifest.yml "
+            "field changes for any pack",
+        ],
+        "migrate": lambda m: {**m, "sdd_version": "2.7.59"},
+    },
 ]
 
 

{sddflow-2.7.58/sdd/packs/sdd-frontend-spa → sddflow-2.7.59/sdd/packs/sdd-backend-service}/.specify/integrations.yml.example

@@ -198,6 +198,13 @@ confluence:
     validate:  "{feature} — Validation Report"
     analyze:   "{feature} — Analysis Report"
     clarify:   "{feature} — Clarifications"
+    tasks:     "{feature} — Tasks"
+    checklist: "{feature} — QA Checklist"
+    qa-testcases: "{feature} — QA Test Cases"
+    data-model:        "Data Model"          # living — no {feature}, nests under {project}
+    security-design:   "Security Design"     # living — no {feature}, nests under {project}
+    api-spec:          "API Specification"   # living — no {feature}, nests under {project}
+    component-library: "Component Library"   # living — no {feature}, nests under {project}
     # release:  "{feature} — Release Notes"
 
   # Diagram rendering: Confluence has NO native Mermaid or PlantUML

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-backend-service/.specify/manifest.yml

@@ -43,5 +43,5 @@ testing_style: "paired"
 # If using sdd-universal instead, set project_type: "backend-service" in its manifest.yml
 # project_type: "backend-service"
 
-sdd_version: "2.7.58"   # set by sdd init; used by sdd upgrade
+sdd_version: "2.7.59"   # set by sdd init; used by sdd upgrade
 ai_tool: ""             # set by sdd init: claude-code | copilot | cursor | windsurf | other

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-backend-service/HOW-TO-USE.md

@@ -679,6 +679,8 @@ sdd confluence push --all        # push all documents listed in integrations.yml
 ```
 Page titles come from `integrations.yml → confluence.page_map`. Re-running updates the existing page.
 
+`page_map` covers every generated doc type by default, not just the phase-gated ones — `qa-testcases`, `tasks`, `checklist`, and the living/service-level docs (`data-model`, `security-design`, `api-spec`, `component-library`) all have an entry, so `sdd confluence push --doc qa-testcases` (for example) works out of the box even though QA test cases have no Jira review gate.
+
 **On a multi-feature project — living docs get ONE page, per-feature docs get one page each.** Living/service-level documents (`data-model`, `security-design`, `api-spec`, `component-library`) always resolve to a single shared page regardless of which feature is active — that's correct, since the underlying document itself is shared. Per-feature documents (`brd`, `use-cases`, `srd`, `design`/`arch`/`hld`/`adr`, `lld`, `validate`, `analyze`, `clarify`, `release`) need `{feature}` in their `page_map` title template to get a separate page per feature — the shipped `integrations.yml.example` already includes it. If your `integrations.yml` predates this and its titles don't have `{feature}`, every feature pushing the same doc type will silently overwrite the same page — add `{feature}` to those entries to fix it.
 
 ---
@@ -706,6 +708,8 @@ sdd review apply  --doc brd      # re-push after addressing reviewer comments
 sdd review status                # dashboard: all documents + their current review state
 ```
 
+**The Confluence page shows the Jira link + status too.** `submit`/`check`/`apply` prepend a small panel to the top of the page — the ticket key (linked), its live status (Pending review / Needs Revision / Approved), and the assigned reviewer role — refreshed every time one of those commands runs, so a reviewer never has to leave Confluence to see where a document stands. Only shown for docs with a `document_reviews` entry; a doc pushed via `page_map` alone (no Jira gate) gets a plain page.
+
 **`sdd review status` needs Jira configured.** For a status view that works
 in **every** review mode (chat, local, or jira), run `sdd dashboard`
 instead — a local web UI with pipeline progress, task status, and token

{sddflow-2.7.58/sdd/packs/sdd-fullstack → sddflow-2.7.59/sdd/packs/sdd-frontend-spa}/.specify/integrations.yml.example

@@ -198,6 +198,13 @@ confluence:
     validate:  "{feature} — Validation Report"
     analyze:   "{feature} — Analysis Report"
     clarify:   "{feature} — Clarifications"
+    tasks:     "{feature} — Tasks"
+    checklist: "{feature} — QA Checklist"
+    qa-testcases: "{feature} — QA Test Cases"
+    data-model:        "Data Model"          # living — no {feature}, nests under {project}
+    security-design:   "Security Design"     # living — no {feature}, nests under {project}
+    api-spec:          "API Specification"   # living — no {feature}, nests under {project}
+    component-library: "Component Library"   # living — no {feature}, nests under {project}
     # release:  "{feature} — Release Notes"
 
   # Diagram rendering: Confluence has NO native Mermaid or PlantUML

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-frontend-spa/.specify/manifest.yml

@@ -32,5 +32,5 @@ testing_style: "paired"
 # If using sdd-universal instead, set project_type: "frontend-spa" in its manifest.yml
 # project_type: "frontend-spa"
 
-sdd_version: "2.7.58"   # set by sdd init; used by sdd upgrade
+sdd_version: "2.7.59"   # set by sdd init; used by sdd upgrade
 ai_tool: ""             # set by sdd init: claude-code | copilot | cursor | windsurf | other

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-frontend-spa/HOW-TO-USE.md

@@ -683,6 +683,8 @@ sdd confluence push --all        # push all documents listed in integrations.yml
 ```
 Page titles come from `integrations.yml → confluence.page_map`. Re-running updates the existing page.
 
+`page_map` covers every generated doc type by default, not just the phase-gated ones — `qa-testcases`, `tasks`, `checklist`, and the living/service-level docs (`data-model`, `security-design`, `api-spec`, `component-library`) all have an entry, so `sdd confluence push --doc qa-testcases` (for example) works out of the box even though QA test cases have no Jira review gate.
+
 **On a multi-feature project — living docs get ONE page, per-feature docs get one page each.** Living/service-level documents (`data-model`, `security-design`, `api-spec`, `component-library`) always resolve to a single shared page regardless of which feature is active — that's correct, since the underlying document itself is shared. Per-feature documents (`brd`, `use-cases`, `srd`, `design`/`arch`/`hld`/`adr`, `lld`, `validate`, `analyze`, `clarify`, `release`) need `{feature}` in their `page_map` title template to get a separate page per feature — the shipped `integrations.yml.example` already includes it. If your `integrations.yml` predates this and its titles don't have `{feature}`, every feature pushing the same doc type will silently overwrite the same page — add `{feature}` to those entries to fix it.
 
 ---
@@ -710,6 +712,8 @@ sdd review apply  --doc brd      # re-push after addressing reviewer comments
 sdd review status                # dashboard: all documents + their current review state
 ```
 
+**The Confluence page shows the Jira link + status too.** `submit`/`check`/`apply` prepend a small panel to the top of the page — the ticket key (linked), its live status (Pending review / Needs Revision / Approved), and the assigned reviewer role — refreshed every time one of those commands runs, so a reviewer never has to leave Confluence to see where a document stands. Only shown for docs with a `document_reviews` entry; a doc pushed via `page_map` alone (no Jira gate) gets a plain page.
+
 **`sdd review status` needs Jira configured.** For a status view that works
 in **every** review mode (chat, local, or jira), run `sdd dashboard`
 instead — a local web UI with pipeline progress, task status, and token

{sddflow-2.7.58/sdd/packs/sdd-backend-service → sddflow-2.7.59/sdd/packs/sdd-fullstack}/.specify/integrations.yml.example

@@ -198,6 +198,13 @@ confluence:
     validate:  "{feature} — Validation Report"
     analyze:   "{feature} — Analysis Report"
     clarify:   "{feature} — Clarifications"
+    tasks:     "{feature} — Tasks"
+    checklist: "{feature} — QA Checklist"
+    qa-testcases: "{feature} — QA Test Cases"
+    data-model:        "Data Model"          # living — no {feature}, nests under {project}
+    security-design:   "Security Design"     # living — no {feature}, nests under {project}
+    api-spec:          "API Specification"   # living — no {feature}, nests under {project}
+    component-library: "Component Library"   # living — no {feature}, nests under {project}
     # release:  "{feature} — Release Notes"
 
   # Diagram rendering: Confluence has NO native Mermaid or PlantUML

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-fullstack/.specify/manifest.yml

@@ -32,5 +32,5 @@ testing_style: "paired"
 # If using sdd-universal instead, set project_type: "fullstack" in its manifest.yml
 # project_type: "fullstack"
 
-sdd_version: "2.7.58"   # set by sdd init; used by sdd upgrade
+sdd_version: "2.7.59"   # set by sdd init; used by sdd upgrade
 ai_tool: ""             # set by sdd init: claude-code | copilot | cursor | windsurf | other

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-fullstack/HOW-TO-USE.md

@@ -685,6 +685,8 @@ sdd confluence push --all        # push all documents listed in integrations.yml
 ```
 Page titles come from `integrations.yml → confluence.page_map`. Re-running updates the existing page.
 
+`page_map` covers every generated doc type by default, not just the phase-gated ones — `qa-testcases`, `tasks`, `checklist`, and the living/service-level docs (`data-model`, `security-design`, `api-spec`, `component-library`) all have an entry, so `sdd confluence push --doc qa-testcases` (for example) works out of the box even though QA test cases have no Jira review gate.
+
 **On a multi-feature project — living docs get ONE page, per-feature docs get one page each.** Living/service-level documents (`data-model`, `security-design`, `api-spec`, `component-library`) always resolve to a single shared page regardless of which feature is active — that's correct, since the underlying document itself is shared. Per-feature documents (`brd`, `use-cases`, `srd`, `design`/`arch`/`hld`/`adr`, `lld`, `validate`, `analyze`, `clarify`, `release`) need `{feature}` in their `page_map` title template to get a separate page per feature — the shipped `integrations.yml.example` already includes it. If your `integrations.yml` predates this and its titles don't have `{feature}`, every feature pushing the same doc type will silently overwrite the same page — add `{feature}` to those entries to fix it.
 
 ---
@@ -712,6 +714,8 @@ sdd review apply  --doc brd      # re-push after addressing reviewer comments
 sdd review status                # dashboard: all documents + their current review state
 ```
 
+**The Confluence page shows the Jira link + status too.** `submit`/`check`/`apply` prepend a small panel to the top of the page — the ticket key (linked), its live status (Pending review / Needs Revision / Approved), and the assigned reviewer role — refreshed every time one of those commands runs, so a reviewer never has to leave Confluence to see where a document stands. Only shown for docs with a `document_reviews` entry; a doc pushed via `page_map` alone (no Jira gate) gets a plain page.
+
 **`sdd review status` needs Jira configured.** For a status view that works
 in **every** review mode (chat, local, or jira), run `sdd dashboard`
 instead — a local web UI with pipeline progress, task status, and token

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-mobile/.specify/integrations.yml.example

@@ -198,6 +198,13 @@ confluence:
     validate:  "{feature} — Validation Report"
     analyze:   "{feature} — Analysis Report"
     clarify:   "{feature} — Clarifications"
+    tasks:     "{feature} — Tasks"
+    checklist: "{feature} — QA Checklist"
+    qa-testcases: "{feature} — QA Test Cases"
+    data-model:        "Data Model"          # living — no {feature}, nests under {project}
+    security-design:   "Security Design"     # living — no {feature}, nests under {project}
+    api-spec:          "API Specification"   # living — no {feature}, nests under {project}
+    component-library: "Component Library"   # living — no {feature}, nests under {project}
     # release:  "{feature} — Release Notes"
 
   # Diagram rendering: Confluence has NO native Mermaid or PlantUML

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-mobile/.specify/manifest.yml

@@ -32,5 +32,5 @@ testing_style: "paired"
 # If using sdd-universal instead, set project_type: "mobile" in its manifest.yml
 # project_type: "mobile"
 
-sdd_version: "2.7.58"   # set by sdd init; used by sdd upgrade
+sdd_version: "2.7.59"   # set by sdd init; used by sdd upgrade
 ai_tool: ""             # set by sdd init: claude-code | copilot | cursor | windsurf | other

{sddflow-2.7.58 → sddflow-2.7.59}/sdd/packs/sdd-mobile/HOW-TO-USE.md

@@ -683,6 +683,8 @@ sdd confluence push --all        # push all documents listed in integrations.yml
 ```
 Page titles come from `integrations.yml → confluence.page_map`. Re-running updates the existing page.
 
+`page_map` covers every generated doc type by default, not just the phase-gated ones — `qa-testcases`, `tasks`, `checklist`, and the living/service-level docs (`data-model`, `security-design`, `api-spec`, `component-library`) all have an entry, so `sdd confluence push --doc qa-testcases` (for example) works out of the box even though QA test cases have no Jira review gate.
+
 **On a multi-feature project — living docs get ONE page, per-feature docs get one page each.** Living/service-level documents (`data-model`, `security-design`, `api-spec`, `component-library`) always resolve to a single shared page regardless of which feature is active — that's correct, since the underlying document itself is shared. Per-feature documents (`brd`, `use-cases`, `srd`, `design`/`arch`/`hld`/`adr`, `lld`, `validate`, `analyze`, `clarify`, `release`) need `{feature}` in their `page_map` title template to get a separate page per feature — the shipped `integrations.yml.example` already includes it. If your `integrations.yml` predates this and its titles don't have `{feature}`, every feature pushing the same doc type will silently overwrite the same page — add `{feature}` to those entries to fix it.
 
 ---
@@ -710,6 +712,8 @@ sdd review apply  --doc brd      # re-push after addressing reviewer comments
 sdd review status                # dashboard: all documents + their current review state
 ```
 
+**The Confluence page shows the Jira link + status too.** `submit`/`check`/`apply` prepend a small panel to the top of the page — the ticket key (linked), its live status (Pending review / Needs Revision / Approved), and the assigned reviewer role — refreshed every time one of those commands runs, so a reviewer never has to leave Confluence to see where a document stands. Only shown for docs with a `document_reviews` entry; a doc pushed via `page_map` alone (no Jira gate) gets a plain page.
+
 **`sdd review status` needs Jira configured.** For a status view that works
 in **every** review mode (chat, local, or jira), run `sdd dashboard`
 instead — a local web UI with pipeline progress, task status, and token