Merge pull request peopleworks#35 from peopleworks/release/0.15.0

Release 0.15.0

Author: peopleworks

CHANGELOG.md

@@ -7,6 +7,40 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.15.0] — 2026-08-23
+
+How it works, not only what exists.
+
+Every release until now answered the same shape of question. What entities does this application
+have. What does this controller do. What does that rule forbid. All of it true, all of it
+declarations — and a business process is not a declaration. It is a path across several of them, and
+nothing in the extractor walked a path.
+
+`xaflogic walkthrough --from ApproveOrder` walks it. The scope is **computed**, by a bounded
+breadth-first traversal, and not chosen by a language model — because a model asked what belongs in
+"the approval process" answers authoritatively, in a form nobody can check, and is wrong in the
+places that look exactly like the places it is right. The Mermaid diagram is emitted from that
+traversal arrow for arrow, for the same reason and more sharply: a diagram is believed at a glance,
+so an invented edge in one is worth less than no diagram at all.
+
+The two halves that make it honest are the ones that took the most care. **A call the walk cannot
+follow is printed rather than dropped** — a virtual method is followed to the declaration written
+beside the call and reported with every override that may replace it, and the document says outright
+that the bodies it never entered mean entities missing from the account. And **`--since` reports what
+changed in that one process** against a stored snapshot, which is the question no conversational
+agent can answer, because none of them has a yesterday.
+
+`--narrate` is opt-in and, deliberately, the least load-bearing thing here. The model receives the
+numbered steps and the code behind them; the only prose that reaches a reader is a paragraph it
+managed to key to a step that exists. A document generated with an empty narration is
+byte-for-byte the one generated with none.
+
+Also in this release: every declaration now says where it is, `file:line`, in the extraction and in
+the MCP tools — the foundation the walkthrough needed and worth having on its own, since the tools
+used to hand an agent a name and leave it to search for it. Four appearance-rule defects, two of
+them found by [@MBrekhof]. Any model can now answer, and a key is enough. And the Markdown we
+generate is Markdown.
+
 ### Added
 
 - **Entities, controllers, actions and methods say where they are declared** ([#23], first step).
@@ -842,7 +876,8 @@ applications; this is the point where it becomes a community project.
 - `XafLogicExplainer.Core` references no DevExpress assemblies and needs no DevExpress license.
   Only the Blazor widget does.
 
-[Unreleased]: https://github.com/peopleworks/XAFLogicExplainer/compare/v0.14.0...HEAD
+[Unreleased]: https://github.com/peopleworks/XAFLogicExplainer/compare/v0.15.0...HEAD
+[0.15.0]: https://github.com/peopleworks/XAFLogicExplainer/releases/tag/v0.15.0
 [0.14.0]: https://github.com/peopleworks/XAFLogicExplainer/releases/tag/v0.14.0
 [0.13.0]: https://github.com/peopleworks/XAFLogicExplainer/releases/tag/v0.13.0
 [0.12.1]: https://github.com/peopleworks/XAFLogicExplainer/releases/tag/v0.12.1

Directory.Build.props

@@ -14,7 +14,7 @@
          Still 0.x deliberately: the extraction engine is production-proven, but this release
          changed its behaviour in six places and has been verified against one real application.
          1.0.0 is earned once the extractor has read codebases we did not write. -->
-    <Version>0.14.0</Version>
+    <Version>0.15.0</Version>
 
     <TargetFramework>net10.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>

README.md

@@ -338,7 +338,7 @@ project is a no-op. There is an MSBuild `.targets` file if you want it to run on
 
 ## Status
 
-**v0.14.0.** The extraction engine is the mature part: it runs in production against real XAF
+**v0.15.0.** The extraction engine is the mature part: it runs in production against real XAF
 applications. The agent-facing surface is what is landing now, in the open.
 
 | | |
@@ -348,6 +348,7 @@ applications. The agent-facing surface is what is landing now, in the open.
 | ✅ | **Custom property and list editors**, their client assets, and built-in editors reconfigured at run time |
 | ✅ | **Version-gated data migrations** — what happened to databases that were not fresh |
 | ✅ | Incremental change detection, diff reports, multi-project, watch mode |
+| ✅ | **Walkthrough** — one process traced end to end, with a diagram emitted from the trace, the calls it could not follow, and `--since` |
 | ✅ | AI enrichment of controllers and actions (`--enrich`) |
 | ✅ | Blazor in-app help panel |
 | ✅ | **`AGENTS.md` / `CLAUDE.md` / Copilot instructions** — zero infrastructure, works for everyone |

plugins/xaf-logic-explainer/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "xaf-logic-explainer",
   "description": "Query a specific DevExpress XAF application: its entities, controllers, actions, business rules and Model Editor customizations, extracted from source with Roslyn.",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "license": "MIT",
   "author": {
     "name": "Pedro Hernández (PeopleWorks)",

plugins/xaf-logic-explainer/skills/xaf-application-knowledge/SKILL.md

@@ -17,7 +17,7 @@ compatibility: >-
   text and never compiles the target project.
 metadata:
   author: PeopleWorks
-  version: "0.14.0"
+  version: "0.15.0"
   repository: https://github.com/peopleworks/XAFLogicExplainer
 ---
 
@@ -56,6 +56,7 @@ One call usually establishes enough to answer, or to know which detail tool to c
 | `xaf_controller` | Asked what a button, command or action actually does — returns the real handler code |
 | `xaf_rules` | Asked what the system requires, forbids or computes |
 | `xaf_model` | Asked how a screen or list is configured |
+| `xaf_walkthrough` | Asked **how** something works, not what exists — traces one process end to end, and names the calls it could not follow |
 | `xaf_refresh` | Only if you believe the cached view is stale; changes are detected automatically |
 
 ## The inventories are complete

src/XafLogicExplainer.Mcp/.mcp/server.json

@@ -1,15 +1,15 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.peopleworks/xaf-logic-explainer",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "title": "XAF Logic Explainer",
   "description": "Query your DevExpress XAF app: entities, controllers, actions, rules, Model Editor.",
   "packages": [
     {
       "registryType": "nuget",
       "registryBaseUrl": "https://api.nuget.org/v3/index.json",
       "identifier": "XafLogicExplainer.Mcp",
-      "version": "0.14.0",
+      "version": "0.15.0",
       "transport": {
         "type": "stdio"
       },