nold-ai
diff --git a/‎AGENTS.md‎
Lines changed: 17 additions & 0 deletions b/‎AGENTS.md‎
Lines changed: 17 additions & 0 deletions
diff --git a/‎CHANGELOG.md‎
Lines changed: 47 additions & 0 deletions b/‎CHANGELOG.md‎
Lines changed: 47 additions & 0 deletions
diff --git a/‎README.md‎
Lines changed: 7 additions & 0 deletions b/‎README.md‎
Lines changed: 7 additions & 0 deletions
diff --git a/‎docs/README.md‎
Lines changed: 7 additions & 0 deletions b/‎docs/README.md‎
Lines changed: 7 additions & 0 deletions
diff --git a/‎docs/getting-started/tutorial-backlog-refine-ai-ide.md‎
Lines changed: 11 additions & 9 deletions b/‎docs/getting-started/tutorial-backlog-refine-ai-ide.md‎
Lines changed: 11 additions & 9 deletions
diff --git a/‎docs/getting-started/tutorial-daily-standup-sprint-review.md‎
Lines changed: 19 additions & 17 deletions b/‎docs/getting-started/tutorial-daily-standup-sprint-review.md‎
Lines changed: 19 additions & 17 deletions
@@ -230,6 +230,23 @@ def my_command(
     console.print("[bold]Processing...[/bold]")
 ```
 
+## Backlog Command Topology
+
+Keep backlog functionality grouped under the common top-level `backlog` command:
+
+- `specfact backlog ceremony standup`
+- `specfact backlog ceremony refinement`
+- `specfact backlog analyze-deps`
+- `specfact backlog delta status|impact|cost-estimate|rollback-analysis`
+- `specfact backlog verify-readiness`
+
+Project-scoped orchestration belongs under `project`:
+
+- `specfact project link-backlog`
+- `specfact project health-check`
+- `specfact project devops-flow --stage <plan|develop|review|release|monitor> --action <...>`
+- `specfact project snapshot|regenerate|export-roadmap`
+
 ## Testing
 
 **Contract-first approach**: `@icontract` contracts on public APIs are the primary coverage mechanism (target 80%+ API coverage). Redundant unit tests that only assert input validation or type checks should be removed because contracts and beartype already cover them.
 
@@ -9,6 +9,53 @@ All notable changes to this project will be documented in this file.
 
 ---
 
+## [0.31.0] - 2026-02-13
+
+### Added
+
+- Backlog dependency-analysis module package (`backlog-core`) with provider-agnostic graph models and analyzers.
+- `specfact backlog` command suite for dependency-centric workflows:
+  - `analyze-deps`
+  - `trace-impact`
+  - `sync`
+  - `verify-readiness`
+  - `diff`
+  - `promote`
+  - `generate-release-notes`
+- Nested backlog delta workflow under `specfact backlog delta`:
+  - `status`
+  - `impact`
+  - `cost-estimate`
+  - `rollback-analysis`
+- Project backlog integration commands:
+  - `specfact project link-backlog`
+  - `specfact project health-check`
+  - `specfact project devops-flow`
+  - `specfact project snapshot`
+  - `specfact project regenerate`
+  - `specfact project export-roadmap`
+
+### Changed
+
+- Backlog command discoverability now follows impact-first ordering with command groups shown before leaf commands.
+- Backlog ceremony workflows are grouped under `specfact backlog ceremony` with clearer subcommands:
+  - `standup`
+  - `refinement`
+- `project regenerate` mismatch UX:
+  - default summary-only output for plan/backlog mismatches
+  - optional `--verbose` for detailed mismatch lines
+  - optional `--strict` to fail on mismatches
+
+### Fixed
+
+- Resolved legacy/duplicate command registration behavior for backlog module integration under a shared `backlog` top-level group.
+- Resolved missing backlog-core lazy-load path in project health/dependency flows (`No module named 'backlog_core'`).
+- Enriched provider dependency extraction for graph analysis:
+  - GitHub: normalized relationship extraction (`blocks`, `blocked by`, related, parent/child conventions) and graph type enrichment
+  - ADO: relationship mapping parity for hierarchy/dependency/related links
+
+---
+
 ## [0.30.4] - 2026-02-12
 
 ### Fixed (0.30.4)
 
@@ -110,6 +110,10 @@ Most tools help **either** coders **or** agile teams. SpecFact does both:
 - **Ceremony support teams can run**: standup, refinement, sprint planning, flow metrics (Scrum/Kanban/SAFe).
 - **Policy + validation**: DoR/DoD/flow checks plus contract enforcement for production-grade stability.
 
+Recommended command entrypoints:
+- `specfact backlog ceremony standup ...`
+- `specfact backlog ceremony refinement ...`
+
 **Try it now**
 
 - **Coders**: [AI IDE Workflow](docs/guides/ai-ide-workflow.md)
@@ -214,6 +218,9 @@ SpecFact complements your stack rather than replacing it.
 - **[Documentation Index](docs/README.md)**
 - **[Command Reference](docs/reference/commands.md)**
 - **[Backlog Refinement](docs/guides/backlog-refinement.md)**
+- **[Backlog Dependency Analysis](docs/guides/backlog-dependency-analysis.md)**
+- **[Backlog Delta Commands](docs/guides/backlog-delta-commands.md)**
+- **[Project DevOps Flow](docs/guides/project-devops-flow.md)**
 - **[Sidecar Validation](docs/guides/sidecar-validation.md)**
 - **[OpenSpec Journey](docs/guides/openspec-journey.md)**
 
 
@@ -19,6 +19,10 @@ Most tools help **either** coders **or** agile teams. SpecFact does both:
 - **Ceremony support teams can run**: standup, refinement, sprint planning, flow metrics (Scrum/Kanban/SAFe).
 - **Policy + validation**: DoR/DoD/flow checks plus contract enforcement for production-grade safety.
 
+Recommended command entrypoints:
+- `specfact backlog ceremony standup ...`
+- `specfact backlog ceremony refinement ...`
+
 **Try it now**
 
 - **Coders**: [AI IDE Workflow](guides/ai-ide-workflow.md)
@@ -103,6 +107,9 @@ For implementation details, see:
 
 - [Agile/Scrum Workflows](guides/agile-scrum-workflows.md)
 - [Backlog Refinement](guides/backlog-refinement.md)
+- [Backlog Dependency Analysis](guides/backlog-dependency-analysis.md)
+- [Backlog Delta Commands](guides/backlog-delta-commands.md)
+- [Project DevOps Flow](guides/project-devops-flow.md)
 - [DevOps Adapter Integration](guides/devops-adapter-integration.md)
 - [AI IDE Workflow](guides/ai-ide-workflow.md)
 - [Sidecar Validation](guides/sidecar-validation.md)
 
@@ -9,14 +9,16 @@ permalink: /getting-started/tutorial-backlog-refine-ai-ide/
 
 This tutorial walks agile DevOps teams through integrating SpecFact CLI backlog refinement with their AI IDE (Cursor, VS Code + Copilot, Claude Code, etc.) using the interactive slash prompt. You will improve backlog story quality, make informed decisions about underspecification, split stories when too big, fix ambiguities, respect Definition of Ready (DoR), and optionally use custom template mapping for advanced teams.
 
+Preferred command path is `specfact backlog ceremony refinement ...`. The legacy `specfact backlog refine ...` path remains supported for compatibility.
+
 **Time**: ~20–30 minutes  
 **Outcome**: End-to-end flow from raw backlog items to template-compliant, DoR-ready stories via your AI IDE.
 
 ---
 
 ## What You'll Learn
 
-- Run `specfact backlog refine` and use the **slash prompt** in your AI IDE for interactive refinement
+- Run `specfact backlog ceremony refinement` and use the **slash prompt** in your AI IDE for interactive refinement
 - Use the **interactive feedback loop**: present story → assess specification level (under-/over-/fit) → list ambiguities → ask clarification → re-refine until approved
 - Improve story quality: identify **underspecified** (missing AC, vague scope), **overspecified** (too many sub-steps, implementation detail), or **fit-for-scope** stories
 - Decide when to **split** stories that are too big
@@ -40,20 +42,20 @@ From your **repo root** (or where your backlog lives):
 
 ```bash
 # GitHub: org/repo are auto-detected from git remote when run from a GitHub clone
-specfact backlog refine github --search "is:open label:feature" --limit 5 --preview
+specfact backlog ceremony refinement github --search "is:open label:feature" --limit 5 --preview
 
 # Or export to a temp file for your AI IDE to process (recommended for interactive loop)
-specfact backlog refine github --export-to-tmp --search "is:open label:feature" --limit 5
+specfact backlog ceremony refinement github --export-to-tmp --search "is:open label:feature" --limit 5
 ```
 
 **Auto-detect from clone**: When you run from a **GitHub** clone (e.g. `https://github.com/owner/repo` or `git@github.com:owner/repo.git`), SpecFact infers `repo_owner` and `repo_name` from `git remote get-url origin`—no `--repo-owner`/`--repo-name` needed. When you run from an **Azure DevOps** clone (e.g. `https://dev.azure.com/org/project/_git/repo`; SSH keys: `git@ssh.dev.azure.com:v3/org/project/repo`; other SSH: `user@dev.azure.com:v3/org/project/repo`), org and project are inferred. Override with `.specfact/backlog.yaml`, env vars (`SPECFACT_GITHUB_REPO_OWNER`, `SPECFACT_ADO_ORG`, etc.), or CLI options when not in the repo or to override.
 
 If you're **not** in a clone, pass adapter context explicitly:
 
 ```bash
-specfact backlog refine github --repo-owner OWNER --repo-name REPO --search "is:open label:feature" --limit 5 --preview
+specfact backlog ceremony refinement github --repo-owner OWNER --repo-name REPO --search "is:open label:feature" --limit 5 --preview
 # or ADO:
-specfact backlog refine ado --ado-org ORG --ado-project PROJECT --state Active --limit 5 --preview
+specfact backlog ceremony refinement ado --ado-org ORG --ado-project PROJECT --state Active --limit 5 --preview
 ```
 
 - Use `--ignore-refined` (default) so `--limit` applies to items that **need** refinement
@@ -104,7 +106,7 @@ If your team uses DoR:
 2. Run refine with `--check-dor`:
 
    ```bash
-   specfact backlog refine github --repo-owner OWNER --repo-name REPO --check-dor --labels feature
+   specfact backlog ceremony refinement github --repo-owner OWNER --repo-name REPO --check-dor --labels feature
    ```
 
 3. In the interactive loop, treat DoR as part of “fit for scope”: if the refined story doesn’t meet DoR (e.g. missing AC or story points), the AI should flag it as under-specified or not ready and suggest what to add.
@@ -127,10 +129,10 @@ When you’re satisfied with the refined content:
 ```bash
 # If you used --export-to-tmp, save the refined file as ...-refined.md, then:
 # (From repo root, org/repo or org/project are auto-detected from git remote)
-specfact backlog refine github --import-from-tmp --write
+specfact backlog ceremony refinement github --import-from-tmp --write
 
 # Or run refine interactively with --write (use with care; confirm each item)
-specfact backlog refine github --write --labels feature --limit 3
+specfact backlog ceremony refinement github --write --labels feature --limit 3
 ```
 
 Use `--preview` (default) until you’re confident; use `--write` only when you want to update the remote backlog.
@@ -144,7 +146,7 @@ If your team uses **custom fields** (e.g. Azure DevOps custom process templates)
 1. **ADO**: Add a custom field mapping file and point the CLI to it:
 
    ```bash
-   specfact backlog refine ado --ado-org ORG --ado-project PROJECT \
+   specfact backlog ceremony refinement ado --ado-org ORG --ado-project PROJECT \
      --custom-field-mapping .specfact/templates/backlog/field_mappings/ado_custom.yaml \
      --state Active
    ```
 
@@ -1,22 +1,24 @@
 ---
 layout: default
 title: Tutorial - Daily Standup and Sprint Review with SpecFact CLI
-description: End-to-end daily standup and sprint review using specfact backlog daily. Auto-detect repo from git (GitHub or Azure DevOps), view standup table, post standup comments, use interactive mode and Copilot export.
+description: End-to-end daily standup and sprint review using specfact backlog ceremony standup. Auto-detect repo from git (GitHub or Azure DevOps), view standup table, post standup comments, use interactive mode and Copilot export.
 permalink: /getting-started/tutorial-daily-standup-sprint-review/
 ---
 
 # Tutorial: Daily Standup and Sprint Review with SpecFact CLI
 
 This tutorial walks you through a complete **daily standup and sprint review** workflow using SpecFact CLI: view your backlog items, optionally post standup comments to issues, use interactive step-through and Copilot export—with **no need to pass org/repo or org/project** when you run from your cloned repo.
 
+Preferred command path is `specfact backlog ceremony standup ...`. The legacy `specfact backlog daily ...` path remains supported for compatibility.
+
 **Time**: ~10–15 minutes  
 **Outcome**: End-to-end flow from "clone + auth" to standup view, optional post, interactive review, and Copilot-ready export.
 
 ---
 
 ## What You'll Learn
 
-- Run **`specfact backlog daily`** and see your standup table (assigned + unassigned items) with **auto-detected** GitHub org/repo or Azure DevOps org/project from the git remote
+- Run **`specfact backlog ceremony standup`** and see your standup table (assigned + unassigned items) with **auto-detected** GitHub org/repo or Azure DevOps org/project from the git remote
 - Use **`.specfact/backlog.yaml`** or environment variables when you're not in the repo (e.g. CI) or to override
 - **Post a standup comment** to the first (or selected) item with `--yesterday`, `--today`, `--blockers` and `--post`
 - Use **`--interactive`** for step-by-step story review (arrow-key selection, full detail, latest comment + hidden-count hint, and optional in-flow posting on the selected story)
@@ -45,11 +47,11 @@ From your **repo root** (where `.git` lives):
 
 ```bash
 # GitHub: org/repo are inferred from git remote origin
-specfact backlog daily github
+specfact backlog ceremony standup github
 
 # Azure DevOps: org/project are inferred from git remote origin
 # (e.g. https://dev.azure.com/... or git@ssh.dev.azure.com:v3/... for SSH keys; user@dev.azure.com:v3/... if not using SSH keys)
-specfact backlog daily ado
+specfact backlog ceremony standup ado
 ```
 
 **What you see**:
@@ -73,13 +75,13 @@ Narrow the list to your sprint or assignee:
 
 ```bash
 # My items only (GitHub: login; ADO: current user)
-specfact backlog daily github --assignee me
+specfact backlog ceremony standup github --assignee me
 
 # Current sprint (when adapter supports it, e.g. ADO)
-specfact backlog daily ado --sprint current
+specfact backlog ceremony standup ado --sprint current
 
 # Open items, limit 10, blockers first
-specfact backlog daily github --state open --limit 10 --blockers-first
+specfact backlog ceremony standup github --state open --limit 10 --blockers-first
 ```
 
 Default scope is **state=open**, **limit=20**; overridable via `SPECFACT_STANDUP_STATE`, `SPECFACT_STANDUP_LIMIT`, or `.specfact/standup.yaml`.
@@ -91,7 +93,7 @@ Default scope is **state=open**, **limit=20**; overridable via `SPECFACT_STANDUP
 To add a **standup comment** to the **first** item in the list, pass **values** for yesterday/today/blockers and `--post`:
 
 ```bash
-specfact backlog daily github \
+specfact backlog ceremony standup github \
   --yesterday "Worked on daily standup and progress support" \
   --today "Will add tests and docs" \
   --blockers "None" \
@@ -109,7 +111,7 @@ specfact backlog daily github \
 For a **refine-like** walkthrough (select item → view full detail → next/previous/back/exit):
 
 ```bash
-specfact backlog daily github --interactive
+specfact backlog ceremony standup github --interactive
 ```
 
 - Use the menu to **select** an item (arrow keys).
@@ -125,7 +127,7 @@ Use **`--suggest-next`** to show a suggested next item by value score (business
 To feed a **summary file** into your AI IDE (e.g. for a Copilot slash-command during standup):
 
 ```bash
-specfact backlog daily github --copilot-export ./standup-summary.md --comments
+specfact backlog ceremony standup github --copilot-export ./standup-summary.md --comments
 ```
 
 The file contains one section per item (ID, title, status, assignees, last updated, progress, blockers).
@@ -141,10 +143,10 @@ To get a **prompt** you can paste into Copilot or feed to a slash command (e.g.
 
 ```bash
 # Print prompt to stdout (copy-paste to Copilot)
-specfact backlog daily github --summarize --comments
+specfact backlog ceremony standup github --summarize --comments
 
 # Write prompt to a file (e.g. for slash command)
-specfact backlog daily github --summarize-to ./standup-prompt.md --comments
+specfact backlog ceremony standup github --summarize-to ./standup-prompt.md --comments
 ```
 
 The output includes an instruction to generate a standup summary, the applied filter context (adapter,
@@ -167,13 +169,13 @@ issues/open questions, discussion notes as comments).
 
    ```bash
    cd /path/to/your-repo
-   specfact backlog daily github
+   specfact backlog ceremony standup github
    ```
 
 3. **Optional: post today's standup** to the first item:
 
    ```bash
-   specfact backlog daily github \
+   specfact backlog ceremony standup github \
      --yesterday "Implemented backlog context and git inference" \
      --today "Docs and tests for daily standup tutorial" \
      --blockers "None" \
@@ -183,9 +185,9 @@ issues/open questions, discussion notes as comments).
 4. **Optional: interactive review** or **Copilot export**:
 
    ```bash
-   specfact backlog daily github --interactive --last-comments 3
+   specfact backlog ceremony standup github --interactive --last-comments 3
    # or
-   specfact backlog daily github --copilot-export ./standup.md
+   specfact backlog ceremony standup github --copilot-export ./standup.md
    ```
 
 ---
@@ -194,7 +196,7 @@ issues/open questions, discussion notes as comments).
 
 | Goal | How |
 |------|-----|
-| View standup without typing org/repo | Run `specfact backlog daily github` or `ado` from **repo root**; org/repo or org/project are **auto-detected** from git remote. |
+| View standup without typing org/repo | Run `specfact backlog ceremony standup github` or `ado` from **repo root**; org/repo or org/project are **auto-detected** from git remote. |
 | Override or use outside repo | Use `.specfact/backlog.yaml`, env vars (`SPECFACT_GITHUB_REPO_OWNER`, etc.), or CLI `--repo-owner`/`--repo-name` or `--ado-org`/`--ado-project`. |
 | Post standup to first item | Use `--yesterday "..."` `--today "..."` `--blockers "..."` and `--post` (values required). |
 | Post standup while reviewing selected story | Use `--interactive` and choose **Post standup update** from navigation. |