@cratis/pi 7.102.0 → 7.103.1

package/package/corpus/skills/dump-collect/references/nativeaot-dumps.md

@@ -0,0 +1,280 @@
+# NativeAOT Crash Dump Collection
+
+## Contents
+
+- OS-Level Core Dumps (Preferred)
+- macOS
+- Windows
+- Alternative: Using createdump with DOTNET_DbgEnableMiniDump
+- Verification
+
+| Need | Tool | Platforms |
+|------|------|-----------|
+| Automatic dump on crash (preferred) | OS-level core dumps (`ulimit`, `core_pattern`, WER) | All |
+| Automatic dump on crash (alternative) | `createdump` + `DOTNET_DbgEnableMiniDump` env vars | All |
+| On-demand from running process | `gcore` (Linux), `lldb` (macOS), `procdump` (Windows) | Per-platform |
+
+NativeAOT applications are native executables. Since NativeAOT only supports full dumps, OS-level core dump mechanisms are the simplest approach — no extra tooling to copy or configure.
+
+> **Note:** NativeAOT only supports full dumps. `DOTNET_DbgMiniDumpType` must be set to `4` (Full).
+
+## OS-Level Core Dumps (Preferred)
+
+### Linux
+
+**Option A: Direct core dumps (simplest)**
+
+```bash
+# Enable core dumps for the current shell session
+ulimit -c unlimited
+
+# Set the core dump output pattern (system-wide, requires root)
+echo '/tmp/dumps/core.%e.%p.%t' | sudo tee /proc/sys/kernel/core_pattern
+
+# Make persistent across reboots — add to /etc/sysctl.conf:
+# kernel.core_pattern = /tmp/dumps/core.%e.%p.%t
+
+# Ensure dump directory exists
+mkdir -p /tmp/dumps
+```
+
+> **Note:** `ulimit` only applies to processes started in the current shell session. For an already-running process, use on-demand collection with `gcore` (see On-Demand Dump Collection below).
+
+**Format specifiers for `core_pattern`:**
+| Spec | Meaning |
+|------|---------|
+| `%p` | PID |
+| `%e` | Executable name (first 15 chars) |
+| `%t` | Unix timestamp |
+| `%h` | Hostname |
+| `%u` | UID |
+
+**Option B: systemd-coredump (systemd systems)**
+
+Many Linux distributions pipe core dumps to `systemd-coredump` by default. Check:
+
+```bash
+cat /proc/sys/kernel/core_pattern
+# If it shows: |/usr/lib/systemd/systemd-coredump ...
+# Then systemd-coredump is already handling dumps.
+```
+
+Using `coredumpctl`:
+
+```bash
+# List collected dumps
+coredumpctl list
+
+# Show details of the most recent dump
+coredumpctl info
+
+# Export a dump to a file
+coredumpctl dump -o /tmp/dumps/myapp.core
+
+# Filter by executable name
+coredumpctl list myapp
+coredumpctl dump myapp -o /tmp/dumps/myapp.core
+```
+
+Configure systemd-coredump storage in `/etc/systemd/coredump.conf`:
+```ini
+[Coredump]
+Storage=external
+MaxUse=2G
+ProcessSizeMax=8G
+```
+
+### On-Demand Dump Collection
+
+```bash
+# Using gcore (from gdb package)
+gcore -o /tmp/dumps/myapp <pid>
+```
+
+## macOS
+
+### Automatic Crash Dumps
+
+```bash
+# Enable core dumps for the current shell session
+ulimit -c unlimited
+
+# Core dumps go to /cores/core.<pid>
+# Ensure the directory exists and is writable
+sudo mkdir -p /cores
+sudo chmod 1777 /cores
+
+# Verify the setting
+ulimit -c  # Should print "unlimited"
+```
+
+**Notes:**
+- macOS also generates `.crash` reports in `~/Library/Logs/DiagnosticReports/` automatically — these are text-based crash logs, not full memory dumps.
+- On Apple Silicon, core dumps may require SIP (System Integrity Protection) adjustments for certain processes.
+
+### Retrieving Dumps from an Already-Crashed Process
+
+If the app has already crashed and core dumps were enabled (`ulimit -c unlimited` was set):
+
+```bash
+# Check /cores/ for core dumps
+ls -la /cores/core.*
+
+# Check macOS crash reports (always generated, even without ulimit)
+ls -la ~/Library/Logs/DiagnosticReports/*.crash
+# Or on newer macOS:
+ls -la ~/Library/Logs/DiagnosticReports/*.ips
+```
+
+If core dumps were **not** enabled before the crash, the core dump is lost. The `.crash`/`.ips` report in `DiagnosticReports` is the only artifact — it contains the stack trace and crash reason but not full memory.
+
+### On-Demand Dump Collection
+
+```bash
+# Using lldb (ships with Xcode command-line tools)
+lldb -p <pid> -o "process save-core /tmp/dumps/myapp.core" -o "quit"
+
+# Using gcore if gdb is installed (via Homebrew)
+gcore -o /tmp/dumps/myapp <pid>
+```
+
+## Windows
+
+### Automatic Crash Dumps (Windows Error Reporting)
+
+WER is a Windows OS-level mechanism — it uses its own `DumpType` values (0=Custom, 1=Mini, 2=Full) which are separate from the `DOTNET_DbgMiniDumpType` environment variable. WER works for any process, including NativeAOT apps without `createdump`.
+
+Configure via the registry. Run in an **elevated PowerShell**:
+
+```powershell
+# Enable local dumps for a specific application
+$appName = "myapp.exe"
+$dumpPath = "C:\dumps"
+$regPath = "HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\$appName"
+
+New-Item -Path $regPath -Force
+New-ItemProperty -Path $regPath -Name "DumpFolder" -Value $dumpPath -PropertyType ExpandString -Force
+New-ItemProperty -Path $regPath -Name "DumpCount" -Value 10 -PropertyType DWord -Force
+New-ItemProperty -Path $regPath -Name "DumpType" -Value 2 -PropertyType DWord -Force
+# DumpType: 0=Custom, 1=Mini, 2=Full
+
+# Ensure dump directory exists
+New-Item -Path $dumpPath -ItemType Directory -Force
+```
+
+**To enable for ALL applications** (not just one), use the parent key:
+```powershell
+$regPath = "HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps"
+New-Item -Path $regPath -Force
+New-ItemProperty -Path $regPath -Name "DumpFolder" -Value "C:\dumps" -PropertyType ExpandString -Force
+New-ItemProperty -Path $regPath -Name "DumpType" -Value 2 -PropertyType DWord -Force
+```
+
+### On-Demand Dump Collection
+
+**Using procdump (recommended — download from Sysinternals):**
+
+```powershell
+# Download procdump (one-time)
+# Cratis: Downloads or installs a tool: requires the user's approval; prefer a pinned version (`dotnet tool install <tool> --version <x>`)
+Invoke-WebRequest -Uri "https://download.sysinternals.com/files/Procdump.zip" -OutFile "$env:TEMP\Procdump.zip"
+Expand-Archive "$env:TEMP\Procdump.zip" -DestinationPath "$env:TEMP\Procdump" -Force
+
+# Capture a full dump
+& "$env:TEMP\Procdump\procdump.exe" -ma <pid> C:\dumps\myapp.dmp
+
+# Capture on crash (waits for an unhandled exception)
+& "$env:TEMP\Procdump\procdump.exe" -ma -e -w <processname> C:\dumps\myapp.dmp
+```
+
+**Using Task Manager:**
+1. Open Task Manager → Details tab
+2. Right-click the process → "Create memory dump file"
+3. Note the output path shown in the dialog
+
+## Alternative: Using createdump with DOTNET_DbgEnableMiniDump
+
+NativeAOT apps also support the `DOTNET_DbgEnableMiniDump` environment variables if `createdump` is available. This gives you the same env-var-based workflow as CoreCLR, but requires copying `createdump` to the right location.
+
+If `createdump` is placed **next to the application binary**:
+
+```bash
+export DOTNET_DbgEnableMiniDump=1
+export DOTNET_DbgMiniDumpType=4
+export DOTNET_DbgMiniDumpName="/tmp/dumps/%e_%p_%t.dmp"
+export DOTNET_EnableCrashReport=1
+```
+
+> **Note:** The `%e`, `%p`, `%h`, `%t` format specifiers in `DOTNET_DbgMiniDumpName` require .NET 7+. On .NET 6, use a literal path instead.
+
+**Setup:** Copy `createdump` from the .NET runtime into the same directory as your published NativeAOT binary:
+
+```bash
+# Linux
+cp /usr/share/dotnet/shared/Microsoft.NETCore.App/<version>/createdump ./publish/
+
+# macOS
+cp /usr/local/share/dotnet/shared/Microsoft.NETCore.App/<version>/createdump ./publish/
+
+# Windows (PowerShell)
+Copy-Item "C:\Program Files\dotnet\shared\Microsoft.NETCore.App\<version>\createdump.exe" .\publish\
+```
+
+**If the .NET runtime is not installed** (fully self-contained deployment), extract `createdump` from the runtime Docker image or NuGet package:
+
+```bash
+# Extract from Docker runtime image
+docker run --rm -v "$(pwd)/publish:/out" mcr.microsoft.com/dotnet/runtime:10.0 \
+  sh -c 'cp /usr/share/dotnet/shared/Microsoft.NETCore.App/*/createdump /out/'
+```
+
+### .NET 11+: DOTNET_DbgCreateDumpToolPath
+
+Starting with .NET 11, you can point to `createdump` at any location instead of requiring it next to the binary:
+
+```bash
+export DOTNET_DbgCreateDumpToolPath=/opt/tools/createdump
+export DOTNET_DbgEnableMiniDump=1
+export DOTNET_DbgMiniDumpType=4
+export DOTNET_DbgMiniDumpName="/tmp/dumps/%e_%p_%t.dmp"
+```
+
+This is especially useful in containers where you can install `createdump` once in a shared location.
+
+## Verification
+
+### When using OS-level core dumps
+
+```bash
+# Linux — check core_pattern and ulimit
+cat /proc/sys/kernel/core_pattern
+ulimit -c
+
+# macOS — check ulimit and /cores/
+ulimit -c
+ls -la /cores/
+
+# Linux (systemd) — check for recent dumps
+coredumpctl list --no-pager | tail -5
+```
+
+```powershell
+# Windows — check WER registry
+Get-ChildItem "HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" -ErrorAction SilentlyContinue
+Get-ChildItem "C:\dumps" -ErrorAction SilentlyContinue
+```
+
+### When using createdump + DOTNET_DbgEnableMiniDump
+
+```bash
+# Verify env vars are set
+env | grep DOTNET_Dbg
+env | grep DOTNET_EnableCrashReport
+
+# Verify createdump is next to the binary (or at DOTNET_DbgCreateDumpToolPath)
+ls -la ./createdump        # co-located
+# or: ls -la $DOTNET_DbgCreateDumpToolPath   # .NET 11+
+
+# Verify dump directory exists
+ls -la /tmp/dumps/
+```

package/package/corpus/skills/eliminate-redundant-restores/LICENSE

@@ -0,0 +1,23 @@
+The MIT License (MIT)
+
+Copyright (c) .NET Foundation and Contributors
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/package/corpus/skills/eliminate-redundant-restores/NOTICE

@@ -0,0 +1,19 @@
+Eliminate Redundant Restores
+Copyright (c) .NET Foundation and Contributors
+Licensed under the MIT License. See LICENSE.
+
+Upstream source: https://github.com/dotnet/skills/blob/a6bf43ab61967c30919334986515163ab24d7635/plugins/dotnet-msbuild/skills/eliminate-redundant-restores/SKILL.md
+
+Changes made by Cratis:
+
+LICENSE:
+- Copy upstream MIT license and copyright verbatim.
+
+SKILL.md:
+- Normalize frontmatter serialization, add MIT license where absent; preserve name and description.
+- Add marked modification/source comment and applicability/Cratis precedence line.
+- Render unimported build-perf-diagnostics routing reference as plain topic text.
+- Render unimported build-perf-baseline routing reference as plain topic text.
+- Rewrite the description to the Cratis shape (what it does, Use when, Not for) and drop references to skills that are not part of this corpus.
+
+NOTICE: Add this attribution, change list, and any download/execution disclosure.

package/package/corpus/skills/eliminate-redundant-restores/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: eliminate-redundant-restores
+description: 'Removes repeated NuGet restores from multi-step .NET builds safely, including Directory.Build.rsp with -restore and safe restore suppression. Use when separate build, test, or publish steps each restore, or when NETSDK1004 or NETSDK1047 appears after --no-restore. Not for a slow first restore, a build with only one restore, version or lock-file errors, or general build slowness without a measured baseline (use the msbuild skill).'
+license: MIT
+---
+
+<!-- Modified by Cratis from dotnet's original (MIT): frontmatter, applicability, navigation and the changes listed in NOTICE. Upstream: https://github.com/dotnet/skills (plugins/dotnet-msbuild/skills/eliminate-redundant-restores/SKILL.md; see NOTICE) -->
+
+# Eliminate Redundant Restores
+
+Cratis rules in `.cratis/ai/rules/` (including `csharp.md`, `specs.csharp.md`, and `orleans.md`) and the `cratis-*` skills win where they differ.
+
+A no-op restore still evaluates every project and checks restore state, so each extra restore in a multi-step build costs seconds to tens of seconds in a large repo. The cure is easy to get wrong: `--no-restore` on a step that no earlier restore actually covered turns a slow build into a failed one. This skill finds which invocations restore, proves which are already covered, and changes only those.
+
+## When to Use
+
+- A pipeline or script runs several `dotnet`/`msbuild` steps and the log shows restore output in more than one of them
+- A restore step exists, yet later steps still print `Determining projects to restore...`
+- A repository `Directory.Build.rsp` or the active MSBuild installation's `MSBuild.rsp` contains `-restore`
+- Someone asks where `--no-restore` or `-restore:false` can safely be added
+- `NETSDK1004` or `NETSDK1047` appeared after `--no-restore` was added
+
+## When Not to Use
+
+- The first restore is slow (feed latency, missing package cache): that is caching, not redundancy
+- There is only one restore across all invocations: nothing to deduplicate
+- Restore errors about versions, lock files or auditing: fix the restore itself
+- Unranked "why is my build slow": start with build perf baseline, then build perf diagnostics
+
+## Inputs
+
+Discover repository inputs in the working directory; do not ask the user for paths.
+
+- CI definitions (`*.yml`, `.github/workflows`, `azure-pipelines*.yml`, `Jenkinsfile`) and build scripts (`build.cmd`, `build.sh`, `build.ps1`, `eng/`)
+- `Directory.Build.rsp`, `Directory.Build.props`/`.targets`, `NuGet.config`
+- Auto-loaded `MSBuild.rsp` beside the active MSBuild executable, or response files passed explicitly with `@file`. A repository-local `MSBuild.rsp` is not auto-loaded
+- Restore evidence if present: step logs or a binlog
+
+## Workflow
+
+### Step 1: Confirm restore is repeated and worth removing
+
+- Log evidence: `Determining projects to restore...` or `All projects are up-to-date for restore.` once per invocation.
+- Binlog evidence: restore evaluations carry the global properties `MSBuildRestoreSessionId` and `ExcludeRestorePackageImports=true`; the Target Performance Summary lists `Restore` with N calls.
+- Quantify each no-op restore. If there is one restore, or the repeated ones total about a second, report "nothing worth removing" and stop without editing.
+
+### Step 2: Inventory every invocation in execution order
+
+| Invocation | Restores? |
+|---|---|
+| `dotnet build`, `test`, `publish`, `pack` | Implicitly, unless `--no-restore`; also check inherited rsp flags |
+| `dotnet run` | Implicitly before building; `--no-restore` can still inherit rsp restore on older SDKs. With `--no-build`, no build or restore runs |
+| `dotnet test`, `publish`, `pack` with `--no-build` | No implicit restore, but an rsp `-restore` can still enable restore; add `--no-restore -restore:false` |
+| `dotnet msbuild`, `msbuild.exe`, CI MSBuild tasks | With `-restore` or `-t:Restore`, including flags inherited from repository `Directory.Build.rsp` or installation-level `MSBuild.rsp`, even when a step looks build-only |
+| `dotnet restore`, `nuget restore`, `msbuild -t:Restore` | Explicit restore |
+| CI build task with a "restore packages" option | Check its default |
+
+Starting with .NET SDK 9.0.1xx, `--no-restore` forwards `-restore:false` to override rsp flags; older SDKs can still inherit `-restore` despite skipping the CLI's implicit restore. Whenever an rsp enables restore, use the version-independent `--no-restore -restore:false` with `dotnet build`, `test`, `publish` or `pack`, even with `--no-build`. `dotnet msbuild` and `msbuild.exe` take `-restore:false`, not `--no-restore`.
+
+`dotnet run` does not expose the MSBuild `-restore:false` override. With an rsp on older SDKs, first build using `dotnet build --no-restore -restore:false`, then run using `dotnet run --no-build` with the same project, configuration, framework and runtime inputs (or execute the built DLL directly). Passing `-restore:false` to `dotnet run` is not a restore-suppression strategy.
+
+### Step 3: Decide per invocation
+
+Keep the first restore. Skip a later one only when all four checks pass:
+
+| Check | If it fails |
+|---|---|
+| **Same project set.** A restore covers its entry project or solution and that project's ProjectReference closure. It does not cover a project in another solution or `.slnf`, a tool built from another path, or a project an orchestrating `.proj` builds through the `MSBuild` task (`-restore` on the orchestrator leaves those unrestored and they fail with NETSDK1004) | Keep restore on that step, or add the project to the explicit restore step |
+| **Same restore inputs.** `-r`/`--runtime`, RID-producing `-a`/`--arch`, `--os`, `--ucr`/`--use-current-runtime`, `TargetFramework(s)`, `RuntimeIdentifier(s)`, `PublishAot`, package sources (`--source`, `--configfile`, `RestoreSources`), `RestorePackagesPath`, and any `-p:` value a PackageReference condition reads. Architecture/OS options combine with the SDK's current RID; `--use-current-runtime` selects it. Missing RID targets fail with NETSDK1047 (`Assets file ... doesn't have a target for 'net10.0/linux-x64'`) | Match the effective RID in the explicit restore (for example `publish --os linux --arch x64` requires `restore -r linux-x64`), or keep restore on the later step. A generic restore does not cover these aliases merely because there is no `-r`. Do not require `SelfContained=true` on restore solely because publish is self-contained: RID-only restore covers ordinary SDK projects. Match `Configuration` or `SelfContained` only if repository conditions change package inputs |
+| **Same available restore state.** Earlier `project.assets.json` files must exist where the later invocation looks for them. Match `--artifacts-path`, `UseArtifactsOutput`/`ArtifactsPath`, and `MSBuildProjectExtensionsPath`/`BaseIntermediateOutputPath`; another job or workspace does not automatically share these files | Align the explicit restore's output layout with build/test, or retain restore in the later workspace. For `build --artifacts-path artifacts --no-restore`, use `restore --artifacts-path artifacts` first; ordinary `obj/` assets do not cover that layout |
+| **Nothing changes packages in between.** A step that generates or edits a project, runs `dotnet add package`, rewrites `Directory.Packages.props` or `NuGet.config` invalidates the earlier restore | Move the explicit restore after that step |
+
+### Step 4: Apply the smallest change
+
+- One explicit restore carrying every restore input, then `--no-restore`, `-restore:false` or `--no-build` on later steps.
+- Several `dotnet test` steps over one solution: build once, then `dotnet test --no-build` on each. Add `--no-restore -restore:false` if an rsp enables restore, including on .NET 8 and earlier. `--no-restore` alone still rebuilds.
+- Keep self-contained publish settings. A `publish --no-build` still needs a prior build with matching configuration, framework, RID and self-contained output; restore compatibility does not prove that build outputs exist.
+- Scope the change to CI and scripts. Leave `-restore` in `Directory.Build.rsp`, because developers rely on it; pass `-restore:false` per invocation instead.
+- Never remove the first restore. If it is a `--locked-mode` gate, keep it there.
+- Do not bundle static graph restore or package caching into this change.
+
+```bash
+# One restore carries every input later steps use
+dotnet restore MyApp.sln -r linux-x64
+# Explicit overrides also work when an rsp enables restore on older SDKs
+dotnet build MyApp.sln -c Release --no-restore -restore:false
+dotnet test MyApp.sln -c Release --no-build --no-restore -restore:false
+dotnet publish src/Api -c Release -r linux-x64 --no-restore -restore:false
+# msbuild invocations need the explicit switch if an rsp file adds -restore
+dotnet msbuild Packaging.proj -t:Pack -restore:false
+```
+
+### Step 5: Validate and report truthfully
+
+1. Run the changed pipeline or script end to end in a clean temporary copy (no `obj/`, no `project.assets.json`). A project that was never restored only fails there. YAML syntax or flag-presence checks do not validate restore coverage or test execution. If you cannot run it, say "not validated" and list the steps and projects to confirm.
+2. Success evidence: every later step passed; `Restore` calls (binlog) or `Determining projects to restore` lines fell from N to the expected count; for a time claim, before/after medians of at least three runs.
+3. Report a restore failure (NETSDK1004, NETSDK1047) separately from a build failure, and never claim success after either.
+
+## Output
+
+Explain which steps restored, which earlier restore covers them, what changed, and what remains unvalidated. State whether redundant restores were removed or no change was needed, keeping the required first restore. Use prose or a findings table as appropriate; no fixed table headings or verdict syntax are required.
+
+## Common Pitfalls
+
+| Pitfall | Solution |
+|---|---|
+| Adding `--no-restore` to every command | Apply the Step 3 checks per step |
+| Missing that an rsp adds `-restore` to "build-only" msbuild steps | Search for `*.rsp` before concluding a step does not restore |
+| Deleting `-restore` from `Directory.Build.rsp` | Override per CI invocation; the rsp serves developers |
+| Orchestrator `.proj` restored, children not | Restore each child explicitly, or keep restore on the step that builds it |
+| Publishing with `-r`, architecture/OS options, or `--use-current-runtime` after a generic restore | Restore with the same effective runtime identifier, including SDK-host defaults used by the aliases |
+| A generator step edits PackageReferences after restore | Restore after the generator |

package/package/corpus/skills/extension-points/LICENSE

@@ -0,0 +1,23 @@
+The MIT License (MIT)
+
+Copyright (c) .NET Foundation and Contributors
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/package/corpus/skills/extension-points/NOTICE

@@ -0,0 +1,18 @@
+MSBuild Extension Points
+Copyright (c) .NET Foundation and Contributors
+Licensed under the MIT License. See LICENSE.
+
+Upstream source: https://github.com/dotnet/skills/blob/a6bf43ab61967c30919334986515163ab24d7635/plugins/dotnet-msbuild/skills/extension-points/SKILL.md
+
+Changes made by Cratis:
+
+LICENSE:
+- Copy upstream MIT license and copyright verbatim.
+
+SKILL.md:
+- Normalize frontmatter serialization, add MIT license where absent; preserve name and description.
+- Add marked modification/source comment and applicability/Cratis precedence line.
+- Render unimported msbuild-antipatterns routing reference as plain topic text.
+- Rewrite the description to the Cratis shape (what it does, Use when, Not for) and drop references to skills that are not part of this corpus.
+
+NOTICE: Add this attribution, change list, and any download/execution disclosure.