sddflow 3.0.2__tar.gz → 3.4.2__tar.gz

sddflow-3.0.2/README.md → sddflow-3.4.2/PKG-INFO

@@ -1,10 +1,46 @@
+Metadata-Version: 2.5
+Name: sddflow
+Version: 3.4.2
+Summary: Spec-Driven Development CLI for AI coding agents — SDLC workflows with Jira/Confluence sync, multi-host PR automation, and live progress dashboards
+Project-URL: Homepage, https://github.com/sunil1983us/sddflow
+Project-URL: Repository, https://github.com/sunil1983us/sddflow
+Project-URL: Bug Tracker, https://github.com/sunil1983us/sddflow/issues
+Project-URL: Changelog, https://github.com/sunil1983us/sddflow/blob/main/CHANGELOG.md
+Author-email: Sunil Kumar <sunil1983.us@gmail.com>
+License: MIT
+Keywords: ai,ai-agent,atlassian,claude,claude-code,code-review,confluence,jira,llm,pull-request,requirements,sdd,sdlc,spec-driven-development,specification
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: click>=8.0
+Requires-Dist: keyring>=24.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: questionary>=2.0
+Requires-Dist: requests>=2.28
+Requires-Dist: rich>=13.0
+Provides-Extra: diagrams
+Requires-Dist: mmdr>=0.3.0; extra == 'diagrams'
+Description-Content-Type: text/markdown
+
 # sddflow (Python) — SDD Framework CLI
 
 [![PyPI version](https://img.shields.io/pypi/v/sddflow.svg?color=blue)](https://pypi.org/project/sddflow/)
 [![Python versions](https://img.shields.io/pypi/pyversions/sddflow.svg)](https://pypi.org/project/sddflow/)
 [![PyPI downloads](https://img.shields.io/pypi/dm/sddflow.svg?color=green)](https://pypistats.org/packages/sddflow)
 [![License](https://img.shields.io/pypi/l/sddflow.svg)](../LICENSE)
-[![CI](https://github.com/sunil1983us/universalguide/actions/workflows/ci.yml/badge.svg)](https://github.com/sunil1983us/universalguide/actions/workflows/ci.yml)
+[![CI](https://github.com/sunil1983us/sddflow/actions/workflows/ci.yml/badge.svg)](https://github.com/sunil1983us/sddflow/actions/workflows/ci.yml)
 
 Python CLI for the SDD (Spec-Driven Development) Framework.  
 Mirrors the Node.js CLI exactly and adds Jira + Confluence integration.
@@ -23,8 +59,8 @@ sdd init
 For development / contributors:
 
 ```bash
-git clone https://github.com/sunil1983us/universalguide.git
-pip install -e ./universalguide/cli-python
+git clone https://github.com/sunil1983us/sddflow.git
+pip install -e ./sddflow/cli-python
 ```
 
 ---
@@ -92,12 +128,46 @@ migration pending, it asks:
   and jumps straight to latest — so an automated `sdd upgrade` never needs
   N reruns to converge.
 
-**This only ever touches `manifest.yml`'s `sdd_version` field.** Fixes made
-to prompt file *content* (`.github/prompts/*.md`, `.claude/commands/*.md`)
-after your project was scaffolded do **not** reach an existing project just
-by running `sdd upgrade` or upgrading the `sddflow` package — those files
-were copied into your project once, at `sdd init` time, and nothing
-re-syncs them automatically. For that, use `--sync-prompts`:
+**On its own, this only touches `manifest.yml`'s `sdd_version` field.**
+Fixes made to your pack's actual files (templates, prompts, commands,
+instructions, setup scripts, and a few IDE-integration files) after your
+project was scaffolded do **not** reach an existing project just by
+running plain `sdd upgrade` or upgrading the `sddflow` package — those
+files were copied into your project once, at `sdd init` time, and nothing
+re-syncs them automatically on its own. Two flags exist for that:
+
+```bash
+sdd upgrade --apply-files               # recommended: every managed file, conflict-aware
+sdd upgrade --sync-prompts              # narrower: prompts + commands only, always overwrites
+```
+
+**`--apply-files`** (recommended) covers everything `sdd doctor` checks —
+`.specify/templates/`, `.claude/commands/`, `.github/prompts/`,
+`.github/instructions/`, `.github/workflows/`, `.cursor/rules/`,
+`.vscode/`, plus `setup.sh`/`setup.ps1` — and tells a safe pack update
+apart from your own hand edits before touching anything:
+
+```bash
+sdd upgrade --apply-files                                # preview + confirm
+sdd upgrade --apply-files --yes                           # skip the confirmation prompt
+sdd upgrade --apply-files --pack sdd-backend-service       # override pack detection
+sdd upgrade --apply-files --force                          # also overwrite locally-modified files
+```
+
+New files and files that still match their last recorded baseline (i.e.
+you never touched them, only the pack moved on) are applied automatically.
+Files that were hand-edited, or that have no recorded baseline to tell an
+update apart from an edit (any project scaffolded before this existed),
+are left alone and listed — pass `--force` to overwrite those too. Every
+file actually overwritten is backed up to
+`.specify/.managed-files-backups/{timestamp}/` first, never silently
+discarded, and a fresh baseline is written after every run so future
+`sdd doctor`/`sdd upgrade --apply-files` calls keep getting more precise.
+See `sdd doctor` below to check drift without changing anything first.
+
+**`--sync-prompts`** is the older, narrower mechanism — `.github/prompts/`
+and `.claude/commands/` only, and always overwrites anything that differs
+(no baseline, no conflict detection) — kept for backward compatibility:
 
 ```bash
 sdd upgrade --sync-prompts              # preview + confirm, then re-copy
@@ -105,20 +175,34 @@ sdd upgrade --sync-prompts --yes        # skip the confirmation prompt
 sdd upgrade --sync-prompts --pack sdd-backend-service   # override pack detection
 ```
 
-Which pack to sync from is resolved, in order: `--pack` flag →
-`manifest.yml`'s `pack` field (written automatically by `sdd init` on
-every new project) → inferred from `project_type` → `sdd-universal` as a
-last resort. If it had to guess, it says so and tells you to pass `--pack`
-if the guess is wrong — projects scaffolded before this field existed
-won't have `pack` recorded, so double-check the inference on those.
-
-Every file about to be overwritten is shown first (and left alone if you
-say no); anything actually overwritten is backed up to
-`.specify/.prompt-sync-backups/{timestamp}/` first, so a project with
-hand-edited prompt files never just loses those edits silently. Only
-`.github/prompts/` and `.claude/commands/` are touched — nothing under
-`.specify/` (templates, constitution, your generated docs) is ever synced
-by this command.
+For both flags, which pack to sync from is resolved, in order: `--pack`
+flag → `manifest.yml`'s `pack` field (written automatically by `sdd init`
+on every new project, and baked as a static default into every pack's own
+`manifest.yml` template as of v3.3.0) → inferred from `project_type` →
+`sdd-universal` as a last resort. If it had to guess, it says so and
+tells you to pass `--pack` if the guess is wrong.
+
+---
+
+### `sdd doctor`
+
+Read-only report of drift between your project's framework-managed files
+and the pack content bundled with your currently installed `sddflow` CLI
+— the same file set `sdd upgrade --apply-files` acts on, but this command
+never changes anything.
+
+```bash
+sdd doctor
+sdd doctor --quiet                      # only show files that aren't up to date
+sdd doctor --pack sdd-backend-service   # check against a specific pack
+```
+
+Each file is classified as up to date, needs update (pack content moved
+on, you never touched it — safe to auto-apply), modified locally (a real
+conflict), differs with no baseline recorded (can't tell an update apart
+from a hand edit — the honest fallback for any project older than this
+baseline mechanism), or missing. Exit code 0 if everything's clean, 1
+otherwise (scriptable in CI).
 
 ---
 

sddflow-3.0.2/PKG-INFO → sddflow-3.4.2/README.md

@@ -1,46 +1,10 @@
-Metadata-Version: 2.4
-Name: sddflow
-Version: 3.0.2
-Summary: Spec-Driven Development CLI for AI coding agents — SDLC workflows with Jira/Confluence sync, multi-host PR automation, and live progress dashboards
-Project-URL: Homepage, https://github.com/sunil1983us/universalguide
-Project-URL: Repository, https://github.com/sunil1983us/universalguide
-Project-URL: Bug Tracker, https://github.com/sunil1983us/universalguide/issues
-Project-URL: Changelog, https://github.com/sunil1983us/universalguide/blob/main/CHANGELOG.md
-Author-email: Sunil Kumar <sunil1983.us@gmail.com>
-License: MIT
-Keywords: ai,ai-agent,atlassian,claude,claude-code,code-review,confluence,jira,llm,pull-request,requirements,sdd,sdlc,spec-driven-development,specification
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3.14
-Classifier: Topic :: Software Development
-Classifier: Topic :: Software Development :: Documentation
-Classifier: Topic :: Utilities
-Requires-Python: >=3.10
-Requires-Dist: click>=8.0
-Requires-Dist: keyring>=24.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: questionary>=2.0
-Requires-Dist: requests>=2.28
-Requires-Dist: rich>=13.0
-Provides-Extra: diagrams
-Requires-Dist: mmdr>=0.3.0; extra == 'diagrams'
-Description-Content-Type: text/markdown
-
 # sddflow (Python) — SDD Framework CLI
 
 [![PyPI version](https://img.shields.io/pypi/v/sddflow.svg?color=blue)](https://pypi.org/project/sddflow/)
 [![Python versions](https://img.shields.io/pypi/pyversions/sddflow.svg)](https://pypi.org/project/sddflow/)
 [![PyPI downloads](https://img.shields.io/pypi/dm/sddflow.svg?color=green)](https://pypistats.org/packages/sddflow)
 [![License](https://img.shields.io/pypi/l/sddflow.svg)](../LICENSE)
-[![CI](https://github.com/sunil1983us/universalguide/actions/workflows/ci.yml/badge.svg)](https://github.com/sunil1983us/universalguide/actions/workflows/ci.yml)
+[![CI](https://github.com/sunil1983us/sddflow/actions/workflows/ci.yml/badge.svg)](https://github.com/sunil1983us/sddflow/actions/workflows/ci.yml)
 
 Python CLI for the SDD (Spec-Driven Development) Framework.  
 Mirrors the Node.js CLI exactly and adds Jira + Confluence integration.
@@ -59,8 +23,8 @@ sdd init
 For development / contributors:
 
 ```bash
-git clone https://github.com/sunil1983us/universalguide.git
-pip install -e ./universalguide/cli-python
+git clone https://github.com/sunil1983us/sddflow.git
+pip install -e ./sddflow/cli-python
 ```
 
 ---
@@ -128,12 +92,46 @@ migration pending, it asks:
   and jumps straight to latest — so an automated `sdd upgrade` never needs
   N reruns to converge.
 
-**This only ever touches `manifest.yml`'s `sdd_version` field.** Fixes made
-to prompt file *content* (`.github/prompts/*.md`, `.claude/commands/*.md`)
-after your project was scaffolded do **not** reach an existing project just
-by running `sdd upgrade` or upgrading the `sddflow` package — those files
-were copied into your project once, at `sdd init` time, and nothing
-re-syncs them automatically. For that, use `--sync-prompts`:
+**On its own, this only touches `manifest.yml`'s `sdd_version` field.**
+Fixes made to your pack's actual files (templates, prompts, commands,
+instructions, setup scripts, and a few IDE-integration files) after your
+project was scaffolded do **not** reach an existing project just by
+running plain `sdd upgrade` or upgrading the `sddflow` package — those
+files were copied into your project once, at `sdd init` time, and nothing
+re-syncs them automatically on its own. Two flags exist for that:
+
+```bash
+sdd upgrade --apply-files               # recommended: every managed file, conflict-aware
+sdd upgrade --sync-prompts              # narrower: prompts + commands only, always overwrites
+```
+
+**`--apply-files`** (recommended) covers everything `sdd doctor` checks —
+`.specify/templates/`, `.claude/commands/`, `.github/prompts/`,
+`.github/instructions/`, `.github/workflows/`, `.cursor/rules/`,
+`.vscode/`, plus `setup.sh`/`setup.ps1` — and tells a safe pack update
+apart from your own hand edits before touching anything:
+
+```bash
+sdd upgrade --apply-files                                # preview + confirm
+sdd upgrade --apply-files --yes                           # skip the confirmation prompt
+sdd upgrade --apply-files --pack sdd-backend-service       # override pack detection
+sdd upgrade --apply-files --force                          # also overwrite locally-modified files
+```
+
+New files and files that still match their last recorded baseline (i.e.
+you never touched them, only the pack moved on) are applied automatically.
+Files that were hand-edited, or that have no recorded baseline to tell an
+update apart from an edit (any project scaffolded before this existed),
+are left alone and listed — pass `--force` to overwrite those too. Every
+file actually overwritten is backed up to
+`.specify/.managed-files-backups/{timestamp}/` first, never silently
+discarded, and a fresh baseline is written after every run so future
+`sdd doctor`/`sdd upgrade --apply-files` calls keep getting more precise.
+See `sdd doctor` below to check drift without changing anything first.
+
+**`--sync-prompts`** is the older, narrower mechanism — `.github/prompts/`
+and `.claude/commands/` only, and always overwrites anything that differs
+(no baseline, no conflict detection) — kept for backward compatibility:
 
 ```bash
 sdd upgrade --sync-prompts              # preview + confirm, then re-copy
@@ -141,20 +139,34 @@ sdd upgrade --sync-prompts --yes        # skip the confirmation prompt
 sdd upgrade --sync-prompts --pack sdd-backend-service   # override pack detection
 ```
 
-Which pack to sync from is resolved, in order: `--pack` flag →
-`manifest.yml`'s `pack` field (written automatically by `sdd init` on
-every new project) → inferred from `project_type` → `sdd-universal` as a
-last resort. If it had to guess, it says so and tells you to pass `--pack`
-if the guess is wrong — projects scaffolded before this field existed
-won't have `pack` recorded, so double-check the inference on those.
-
-Every file about to be overwritten is shown first (and left alone if you
-say no); anything actually overwritten is backed up to
-`.specify/.prompt-sync-backups/{timestamp}/` first, so a project with
-hand-edited prompt files never just loses those edits silently. Only
-`.github/prompts/` and `.claude/commands/` are touched — nothing under
-`.specify/` (templates, constitution, your generated docs) is ever synced
-by this command.
+For both flags, which pack to sync from is resolved, in order: `--pack`
+flag → `manifest.yml`'s `pack` field (written automatically by `sdd init`
+on every new project, and baked as a static default into every pack's own
+`manifest.yml` template as of v3.3.0) → inferred from `project_type` →
+`sdd-universal` as a last resort. If it had to guess, it says so and
+tells you to pass `--pack` if the guess is wrong.
+
+---
+
+### `sdd doctor`
+
+Read-only report of drift between your project's framework-managed files
+and the pack content bundled with your currently installed `sddflow` CLI
+— the same file set `sdd upgrade --apply-files` acts on, but this command
+never changes anything.
+
+```bash
+sdd doctor
+sdd doctor --quiet                      # only show files that aren't up to date
+sdd doctor --pack sdd-backend-service   # check against a specific pack
+```
+
+Each file is classified as up to date, needs update (pack content moved
+on, you never touched it — safe to auto-apply), modified locally (a real
+conflict), differs with no baseline recorded (can't tell an update apart
+from a hand edit — the honest fallback for any project older than this
+baseline mechanism), or missing. Exit code 0 if everything's clean, 1
+otherwise (scriptable in CI).
 
 ---
 

{sddflow-3.0.2 → sddflow-3.4.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "sddflow"
-version = "3.0.2"
+version = "3.4.2"
 description = "Spec-Driven Development CLI for AI coding agents — SDLC workflows with Jira/Confluence sync, multi-host PR automation, and live progress dashboards"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -56,10 +56,10 @@ diagrams = [
 sdd = "sdd.__main__:cli"
 
 [project.urls]
-Homepage = "https://github.com/sunil1983us/universalguide"
-Repository = "https://github.com/sunil1983us/universalguide"
-"Bug Tracker" = "https://github.com/sunil1983us/universalguide/issues"
-Changelog = "https://github.com/sunil1983us/universalguide/blob/main/CHANGELOG.md"
+Homepage = "https://github.com/sunil1983us/sddflow"
+Repository = "https://github.com/sunil1983us/sddflow"
+"Bug Tracker" = "https://github.com/sunil1983us/sddflow/issues"
+Changelog = "https://github.com/sunil1983us/sddflow/blob/main/CHANGELOG.md"
 
 [tool.hatch.build.targets.wheel]
 packages = ["sdd"]

sddflow-3.4.2/sdd/__init__.py

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

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/__main__.py

@@ -5,6 +5,7 @@ from sdd.commands.config import config_command
 from sdd.commands.confluence import confluence_command
 from sdd.commands.cr import cr_command
 from sdd.commands.dashboard import dashboard_command
+from sdd.commands.doctor import doctor_command
 from sdd.commands.feature import feature_command
 from sdd.commands.hooks import hooks_command
 from sdd.commands.init import init_command
@@ -16,7 +17,10 @@ from sdd.commands.token_log import token_log_command
 from sdd.commands.upgrade import upgrade_command
 
 
-@click.group()
+@click.group(
+    epilog="Found a bug or have a feature request? "
+    "https://github.com/sunil1983us/sddflow/issues"
+)
 @click.version_option(__version__, prog_name="sdd")
 def cli():
     """SDD Framework CLI — Spec-Driven Development"""
@@ -35,6 +39,7 @@ cli.add_command(token_log_command, name="token-log")
 cli.add_command(project_type_command, name="project-type")
 cli.add_command(feature_command, name="feature")
 cli.add_command(hooks_command, name="hooks")
+cli.add_command(doctor_command, name="doctor")
 
 
 if __name__ == "__main__":

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/config.py

@@ -1,5 +1,6 @@
 from __future__ import annotations
 
+import json
 import re
 from pathlib import Path
 
@@ -517,31 +518,65 @@ def config_test(profile):
         console.print(f"  [dim]Confluence profile: {cf_name}[/dim]")
         console.print()
 
+    _probe_service(
+        "Jira",
+        lambda: JiraClient(
+            jira_session, jira_prof.base_url, deployment=jira_prof.deployment
+        ).get_myself(),
+        ("displayName", "emailAddress"),
+    )
+    _probe_service(
+        "Confluence",
+        lambda: ConfluenceClient(
+            cf_session, cf_prof.base_url, deployment=cf_prof.deployment
+        ).get_myself(),
+        ("displayName", "username"),
+    )
+
+    console.print()
+
+
+def _probe_service(label: str, get_myself_fn, name_keys: tuple[str, ...]) -> None:
+    """Runs a get_myself()-style connectivity probe and prints one status
+    line -- never lets it crash the whole `sdd config test` command.
+
+    Three failure modes, told apart because each points at a different
+    fix:
+    - HTTPError: the server itself said no (4xx/5xx) -- its status code
+      and body are the most useful thing to show.
+    - JSONDecodeError (raised by response.json() on a 200-but-non-JSON
+      body -- caught as the bare stdlib class since older `requests`
+      versions raise that directly, and as InvalidJSONError to also
+      catch requests>=2.27's own subclass that wraps it): most commonly
+      means base_url points at an SSO/login redirect page or the wrong
+      path entirely, not the real API root -- a raw "Expecting value:
+      line 1 column 1" message (what this looks like uncaught) gives the
+      user no clue what actually went wrong.
+    - Any other RequestException (connection refused, DNS failure,
+      timeout, TLS error, malformed URL): whatever requests' own message
+      says is usually clear enough on its own.
+    """
     try:
-        me = JiraClient(jira_session, jira_prof.base_url).get_myself()
-        name = me.get("displayName") or me.get("emailAddress", "?")
+        me = get_myself_fn()
+        name = next((me.get(k) for k in name_keys if me.get(k)), "?")
         console.print(
-            f"  [green]✓[/green]  Jira       — connected as [cyan]{name}[/cyan]"
+            f"  [green]✓[/green]  {label:<10} — connected as [cyan]{name}[/cyan]"
         )
-    except requests.HTTPError as e:
+    except requests.exceptions.HTTPError as e:
         console.print(
-            f"  [red]✗  Jira       — HTTP {e.response.status_code}: "
+            f"  [red]✗  {label:<10} — HTTP {e.response.status_code}: "
             f"{e.response.text[:120]}[/red]"
         )
-
-    try:
-        me = ConfluenceClient(cf_session, cf_prof.base_url).get_myself()
-        name = me.get("displayName") or me.get("username", "?")
-        console.print(
-            f"  [green]✓[/green]  Confluence — connected as [cyan]{name}[/cyan]"
-        )
-    except requests.HTTPError as e:
+    except (json.JSONDecodeError, requests.exceptions.InvalidJSONError):
         console.print(
-            f"  [red]✗  Confluence — HTTP {e.response.status_code}: "
-            f"{e.response.text[:120]}[/red]"
+            f"  [red]✗  {label:<10} — got a response, but it wasn't "
+            f"JSON.[/red]\n"
+            f"      [dim]Check base_url points at the API root (not a "
+            f"login/SSO redirect page), and that the PAT/token is "
+            f"still valid.[/dim]"
         )
-
-    console.print()
+    except requests.exceptions.RequestException as e:
+        console.print(f"  [red]✗  {label:<10} — {e}[/red]")
 
 
 @config_command.command("fields")
@@ -577,7 +612,7 @@ def config_fields(profile, project):
         )
         raise SystemExit(1)
 
-    fields = JiraClient(session, prof.base_url).get_fields()
+    fields = JiraClient(session, prof.base_url, deployment=prof.deployment).get_fields()
     custom = sorted(
         [f for f in fields if f.get("custom")],
         key=lambda f: f.get("name", ""),

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/confluence.py

@@ -342,7 +342,7 @@ def confluence_push(profile, feature, doc, summary, dry_run, force):
         console.print(f"  [red]✗  Auth error: {e}[/red]")
         raise SystemExit(1)
 
-    client = ConfluenceClient(session, prof.base_url)
+    client = ConfluenceClient(session, prof.base_url, deployment=prof.deployment)
 
     for key, md_path, title in available:
         body, attachments, diagram_warnings = md_to_storage(
@@ -471,7 +471,7 @@ def confluence_draft(doc, profile, feature, dry_run, force):
         console.print(f"  [red]✗  Auth error: {e}[/red]")
         raise SystemExit(1)
 
-    client = ConfluenceClient(session, prof.base_url)
+    client = ConfluenceClient(session, prof.base_url, deployment=prof.deployment)
     body, attachments, diagram_warnings = md_to_storage(
         doc_path.read_text(), cf_cfg.diagrams
     )
@@ -577,7 +577,7 @@ def confluence_pull(doc, profile, feature, page_id):
         console.print(f"  [red]✗  Auth error: {e}[/red]")
         raise SystemExit(1)
 
-    client = ConfluenceClient(session, prof.base_url)
+    client = ConfluenceClient(session, prof.base_url, deployment=prof.deployment)
 
     console.print(f"  Fetching page [cyan]{resolved_page_id}[/cyan] from Confluence...")
     try:

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/cr.py

@@ -122,7 +122,9 @@ def cr_submit(cr, profile, feature, reviewer, dry_run):
 
     # ── Push CR record to Confluence ─────────────────────────────────────────
     if cfg.confluence:
-        cf_client = ConfluenceClient(cf_session, cf_prof.base_url)
+        cf_client = ConfluenceClient(
+            cf_session, cf_prof.base_url, deployment=cf_prof.deployment
+        )
         body_html, attachments, diagram_warnings = md_to_storage(
             cr_text, cfg.confluence.diagrams
         )
@@ -159,7 +161,9 @@ def cr_submit(cr, profile, feature, reviewer, dry_run):
 
     # ── Create / update Jira review task ─────────────────────────────────────
     if cfg.jira:
-        jira_client = JiraClient(jira_session, jira_prof.base_url)
+        jira_client = JiraClient(
+            jira_session, jira_prof.base_url, deployment=jira_prof.deployment
+        )
         # feature_name included for the same reason page_title above is --
         # cr_id alone (e.g. "CHG-001") is scoped per feature's own tasks.md
         # counter, not globally unique across the project. Without it here,
@@ -288,7 +292,7 @@ def cr_check(cr, profile, feature):
     proj = manifest.get("project") or {}
     feature_name = feature or proj.get("feature", "")
 
-    client = JiraClient(session, prof.base_url)
+    client = JiraClient(session, prof.base_url, deployment=prof.deployment)
     # Must match cr_submit's idempotency_label exactly (feature-qualified) --
     # otherwise this would never find the ticket cr_submit actually created.
     issue = client.find_by_label(

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/dashboard.py

@@ -201,12 +201,14 @@ def _fetch_review_links(feature: str) -> dict:
     try:
         if cfg.jira:
             prof, session = load_jira_session(cfg)
-            jira_client = JiraClient(session, prof.base_url)
+            jira_client = JiraClient(session, prof.base_url, deployment=prof.deployment)
         else:
             jira_client = None
         if cfg.confluence:
             cf_prof, cf_session = load_confluence_session(cfg)
-            cf_client = ConfluenceClient(cf_session, cf_prof.base_url)
+            cf_client = ConfluenceClient(
+                cf_session, cf_prof.base_url, deployment=cf_prof.deployment
+            )
         else:
             cf_prof, cf_client = None, None
     except Exception as e:
@@ -305,7 +307,7 @@ def _jira_client_for_comments():
         return None
     try:
         prof, session = load_jira_session(cfg)
-        return JiraClient(session, prof.base_url), cfg
+        return JiraClient(session, prof.base_url, deployment=prof.deployment), cfg
     except Exception:
         return None
 

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/dashboard_static/page.html

@@ -49,6 +49,9 @@ __SDD_DASHBOARD_CSS__
     </div>
   </details>
   <div id="root"></div>
+  <footer class="dashboard-footer">
+    <a href="https://github.com/sunil1983us/sddflow/issues" target="_blank" rel="noopener">Report a bug / request a feature</a>
+  </footer>
 
 <script>
 __SDD_DASHBOARD_THEME_JS__

{sddflow-3.0.2 → sddflow-3.4.2}/sdd/commands/dashboard_static/style.css

@@ -237,4 +237,12 @@
   .pager {
     display: flex; align-items: center; gap: .6rem; margin-top: .6rem;
     padding-top: .6rem; border-top: 1px solid var(--border);
-  }
+  }
+
+  /* Static -- lives in page.html outside #root, so it survives every 5s
+     poll's innerHTML rebuild without needing any JS of its own. */
+  .dashboard-footer {
+    text-align: center; padding: 1.5rem 1rem 2rem; font-size: .8rem;
+  }
+  .dashboard-footer a { color: var(--muted); text-decoration: none; }
+  .dashboard-footer a:hover { color: var(--accent); text-decoration: underline; }