Cleaning

.agents/skills/.gitignore

@@ -0,0 +1,7 @@
+# This directory is copied into consuming repositories by Purview.DotNetProjectSdk
+# so AI agents can discover the bundled skills.
+# Keep this file if you want the generated skill content to stay out of source control.
+# To disable generation entirely, set <EnableEmbeddedAgentSkills>false</EnableEmbeddedAgentSkills>
+# in your project or Directory.Build.props.
+*
+!.gitignore

.agents/skills/changesets-prerelease/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: changesets-prerelease
+description: Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release.
+---
+
+# Changesets Prerelease Skill
+
+Use this skill when preparing the next prerelease version in this repository.
+
+## Steps
+
+1. Add a new changeset:
+   - `npx @changesets/cli add --empty --message "<summary>"`
+   - update the generated `.changeset/*.md` frontmatter with:
+     - `"purview-eventsourcing": patch`
+   - replace the placeholder body with a concise summary of the **actual user-facing changes since the last shipped release**, not just a generic "prepare prerelease" note.
+   - if the immediately previous prerelease number (for example `.24`) has **not** been released yet and you are preparing `.25`, the new markdown should still describe the cumulative changes that matter for the next published prerelease.
+2. Bump versions/changelog:
+   - `npx @changesets/cli version`
+3. Commit the resulting changes (`package.json`, `CHANGELOG.md`, and consumed `.changeset` files).
+
+## Writing the new `.changeset/*.md` body
+
+- Summarize the functional changes that should appear in the changelog for the next published prerelease.
+- Prefer short release-note language such as:
+  - fixed SQL snapshot translation for directly mapped complex mirror properties
+  - clarified provider documentation for scalar value object query behavior
+  - aligned repo-local agent skills and instructions
+- Do **not** leave the body as a procedural placeholder such as `Prepare next prerelease` unless there were truly no meaningful changes.
+- If multiple unreleased prerelease bumps exist locally, write the new file so the generated changelog entry remains useful to an external consumer reading the next shipped release.
+
+## Notes
+
+- Repository currently runs prerelease mode with `tag: prerelease` (`.changeset/pre.json`).
+- Releasing is done from `package.json` version in the `release.yml` workflow.
+- In prerelease mode, `changeset version` can record a changeset in `.changeset/pre.json` even if the new file was created with placeholder/empty content first. If that happens, correct the `.md` frontmatter/body before finalizing the release notes so the next shipped prerelease entry is accurate.

.agents/skills/tunit-test-runner/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: tunit-test-runner
+description: >-
+  Run, filter, and select TUnit tests through `dotnet test`. Use this whenever
+  executing .NET tests in a project that depends on TUnit (built on
+  Microsoft.Testing.Platform / MTP, not VSTest), when `dotnet test --filter`
+  reports "Zero tests ran", or when tests must be narrowed by assembly,
+  namespace, class, test name, [Category], or other custom properties. Covers
+  the `--treenode-filter` path-based query syntax, its operators, the `--`
+  separator rules across SDK versions, and common 0-tests troubleshooting.
+license: MIT
+---
+
+# Running TUnit tests with `dotnet test`
+
+## The one rule that matters most
+
+TUnit runs on **Microsoft.Testing.Platform (MTP)**, not VSTest. The reflexive
+`dotnet test --filter "Category=X"` **does not work**: MTP silently rejects the
+`--filter` flag, prints its own help text, and exits with `Zero tests ran`. That
+looks like a passing-but-empty run or a config failure, but it is just an
+unrecognised flag. **Never reach for `--filter` on a TUnit project.** Use
+`--treenode-filter` instead.
+
+| Other frameworks (VSTest)                  | TUnit (MTP)                                          |
+| ------------------------------------------ | ---------------------------------------------------- |
+| `--filter "Category=Integration"`          | `--treenode-filter "/*/*/*/*[Category=Integration]"` |
+| `--filter "FullyQualifiedName~LoginTests"` | `--treenode-filter "/*/*/LoginTests/*"`              |
+| `--filter "Name=AcceptCookiesTest"`        | `--treenode-filter "/*/*/*/AcceptCookiesTest"`       |
+
+## How to invoke it
+
+Prefer `dotnet test` over `dotnet run`: `dotnet test` builds and runs every
+targeted TFM automatically and works against a `.csproj`, `.sln`, or `.slnx`,
+whereas `dotnet run` only runs a single TFM.
+
+The catch is the `--` separator, which depends on the SDK:
+
+```bash
+# Universal form — works on every SDK. Use this by default.
+dotnet test -- --treenode-filter "/*/*/LoginTests/*"
+
+# .NET 10+ SDK only — the platform flag can be passed directly.
+dotnet test --treenode-filter "/*/*/LoginTests/*"
+```
+
+Anything after `--` is passed through to the TUnit test runner rather than to
+the `dotnet test` command itself. Flags from extension packages
+(`--coverage`, `--report-trx`, `--results-directory`, etc.) **must** also sit
+after the `--`:
+
+```bash
+dotnet test --configuration Release --no-build \
+  -- --treenode-filter "/*/*/*/*[Category=Unit]" --coverage --report-trx
+```
+
+> Run with no filter to execute everything: `dotnet test`.
+
+## The `--treenode-filter` syntax
+
+A filter is a path with four segments, optionally annotated with a property
+group on any segment:
+
+```
+/<Assembly>/<Namespace>/<Class>/<TestName>[Property=Value]
+```
+
+Use `*` as a wildcard in any segment. The classic "run all tests" filter is
+`/*/*/*/*` — four wildcards, one per level.
+
+### Operators
+
+| Operator | Meaning                                       | Example                                |
+| -------- | --------------------------------------------- | -------------------------------------- |
+| `*`      | Wildcard within a segment                     | `/*/*/LoginTests*/*`                   |
+| `=`      | Property equals (exact)                       | `/*/*/*/*[Category=Unit]`              |
+| `!=`     | Property not equal (exclude)                  | `/*/*/*/*[Category!=Slow]`             |
+| `&`      | AND — within one segment / property group     | `/**[(Category=Unit)&(Priority=High)]` |
+| `\|`     | OR — within one segment / property group      | `/*/*/(LoginTests)\|(SignupTests)/*`   |
+| `**`     | Match any path depth (must be at the **end**) | `/MyAssembly/**`                       |
+
+### Two grammar rules that are easy to get wrong
+
+1. **`&` and `|` operate _inside a single segment or property group_, and each
+   side must be wrapped in parentheses.** They do not join two complete paths.
+2. **Only one property group `[...]` is allowed per path segment.** Combine
+   conditions _inside_ the single bracket — do not chain brackets.
+3. **`**` must terminate the path.** `/MyAssembly/**` is valid; `/**/Class/*`
+   is not.
+
+## Troubleshooting: "Zero tests ran" / 0 tests discovered
+
+Check, in order:
+
+1. **`--filter` was used instead of `--treenode-filter`.** This is the most common cause.
+2. **`Microsoft.NET.Test.Sdk` is still referenced.** It conflicts with the TUnit MTP platform.
+3. **TUnit package missing.** Ensure `<PackageReference Include="TUnit" Version="*" />`.
+4. **Missing `[Test]` attribute** or unsupported method shape.
+5. **Wrong `OutputType`.** A `hostfxr.dll could not be found` error means the project needs `<OutputType>Exe</OutputType>`.
+6. **Bad filter shape.** Remember the path has exactly four segments.
+
+## References
+
+- TUnit — Test Filters: https://tunit.dev/docs/execution/test-filters/
+- TUnit — Troubleshooting & FAQ: https://tunit.dev/docs/troubleshooting/
+- TUnit — CI/CD pipelines: https://tunit.dev/docs/examples/tunit-ci-pipeline/
+- TUnit — Explicit tests: https://tunit.dev/docs/writing-tests/explicit/
+- MTP graph-query filtering spec: https://github.com/microsoft/testfx/blob/main/docs/mstest-runner-graphqueryfiltering/graph-query-filtering.md

.changeset/bumpy-crabs-double.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+fixed GetOrCreateAsync always calling creator func/ action

.changeset/bumpy-symbols-learn.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+fixed GetOrCreate that called created func regardless of state

.changeset/chubby-suns-fry.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+added EF support for complex value objects

.changeset/fuzzy-adults-battle.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+fixed the valueobject EF ctor generation not covering all valueobject types

.changeset/major-flies-repeat.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+fixed another GetOrCreateAsync issue calling creator action/ func on non-new aggregates

.changeset/pre.json

@@ -5,20 +5,29 @@
     "purview-eventsourcing": "2.0.0-prerelease.0"
   },
   "changesets": [
+    "bumpy-crabs-double",
+    "bumpy-symbols-learn",
+    "chubby-suns-fry",
     "clean-papayas-hang",
     "curvy-bushes-strive",
     "eager-bikes-hope",
     "early-dryers-slide",
     "eight-walls-report",
     "famous-rice-enter",
+    "fuzzy-adults-battle",
     "large-ideas-vanish",
     "little-moose-buy",
+    "major-flies-repeat",
     "new-grapes-drive",
     "pink-parks-brush",
     "shy-fans-show",
+    "slick-hotels-float",
     "tasty-moose-tickle",
+    "three-ends-nail",
     "two-moose-hug",
     "two-wasps-yell",
+    "violet-files-turn",
+    "wacky-eagles-punch",
     "wild-trees-shout",
     "witty-chefs-find"
   ]

.changeset/slick-hotels-float.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+added an inmemory event and snapshot store for testing

.changeset/three-ends-nail.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+fix: added telemetry activity source and meter names

.changeset/violet-files-turn.md

@@ -0,0 +1,7 @@
+---
+"purview-eventsourcing": patch
+---
+
+- fixed SQL snapshot support for directly mapped complex mirror properties, including deep query translation over `ParserReportSummary` members
+- clarified SQL snapshot/query documentation for provider-converted scalar value objects vs directly mapped complex mirrors
+- aligned repo-local agent instructions and skills under `.agents/skills`

.changeset/wacky-eagles-punch.md

@@ -0,0 +1,5 @@
+---
+"purview-eventsourcing": patch
+---
+
+added IEquatible for value object structs

.github/copilot-instructions.md

@@ -4,7 +4,7 @@ Follow `AGENTS.md`.
 
 Prefer repository-local guidance from:
 
-- `.github/skills/`
-- `.agents/skills/`
+- `src/skills/`
+- `.agents/skills/` (workflow/tooling skills)
 - `.agents/agents/`
 - `.agents/instructions/`