Cut 0.16.0 — what we cannot see, said out loud - #48
Merged
Conversation
Reports are read, which was the largest gap left in the extraction, and the answer about them is three sentences rather than a list: all of them, a lower bound, or unknown rather than zero. The last is the common case, because with ReportsModuleV2 registered the reports live in a database and not in the repository. The same correction reached the framework catalog, wrong for three releases: the newest catalog on the machine was used for every application whatever it targeted, unqualified. Version moved in six places: Directory.Build.props, both fields of .mcp/server.json, plugin.json, the SKILL frontmatter and the README's status line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W45tzJFX3NoSrk7svtQeKT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the release. Does not publish it — the tag, the GitHub Release and the NuGet push stay yours.
What is in it
AGENTS.mdand a newxaf_reportsMCP tool, with the boundThe headline
Every release so far promised: here is something in your application you could not see from the code. This one keeps that promise — reports were the largest gap left — and then does the opposite thing, which turns out to matter more.
An XAF application's reports are frequently not in its repository at all. So the answer stopped being a list and became three sentences: all of them, a lower bound, or unknown rather than zero. That last one is the common case and the one where a confident tool does real damage.
The same correction reached the catalog, where it had been wrong since 0.12.0.
Version moved in six places
Directory.Build.props· both fields of.mcp/server.json·plugin.json· the SKILL frontmatter · the README status line.Six, not the five I had on file — the README carries one too, and it had been stale before.
Checked
Builds clean, 457 tests, zero warnings. Every
0.15.0outside the changelog is gone.Note before you merge
0.15.0 shipped earlier today. Two releases in one day is unusual, and it is your call rather than mine. My read is that it is right anyway: reports are the largest capability added since the walkthrough, and the catalog defect is silently wrong for anyone whose DevExpress version is not the one their catalog was built from — which, on the seven applications checked here, was six of them.
If you would rather let it accumulate, nothing breaks: the branch keeps, and anything Martin lands next folds in.
🤖 Generated with Claude Code
https://claude.ai/code/session_01W45tzJFX3NoSrk7svtQeKT