@cratis/pi 7.115.0 → 7.116.1

package/package/corpus/harnesses/copilot/instructions/github-actions.instructions.md

@@ -115,6 +115,9 @@ capacity numbers into workflows or guidance.
   content the source repository's CI verified before the rollout, may carry
   `[skip ci]` once the same wrapper content has landed with CI running in one canary
   repository. Package-update bots, and any commit touching another file, keep normal CI.
+- Never put a skip token in a pull request title or an ordinary commit message: a
+  merge commit inherits the pull request title, so GitHub then runs nothing on the
+  default branch. See `cratis-engineering-release-trains`.
 - Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
   (for example `contains(github.event.comment.body, '@claude')`) so a runner only
   starts when the agent is actually addressed.
@@ -127,3 +130,9 @@ capacity numbers into workflows or guidance.
   four unintended releases on 2026-08-25.
 - Every repository's release-intent gate must accept `no-release`; a gate that only
   accepts `major`/`minor`/`patch` forces exactly that mistake.
+- Do not merge a pull request that changes `.github/workflows/` while a release Publish
+  run in the same repository has not created its tag yet. `GITHUB_TOKEN` cannot tag a
+  commit whose workflows differ from the default branch, and rerunning fails the same
+  way. Recover with the Publish `workflow_dispatch` from current main.
+- A release-verify job asserts that the GitHub release `v<version>` exists. A watch
+  picks the exact run by head SHA, never by a time window.

package/package/corpus/harnesses/copilot/instructions/specs.csharp.instructions.md

@@ -86,6 +86,10 @@ _service.DidNotReceive().DoSomethingElse(Arg.Any<int>());
 _handler.Handle(Arg.Any<CommandContext>()).Throws(new Exception("fail"));
 ```
 
+A change to a widely substituted interface runs the whole affected spec project,
+not one spec. Grep for `Substitute.For<IThatInterface>` to find every substitute
+that needs updating.
+
 Catch exceptions for a unit under test with `Catch.Exception`:
 
 ```csharp

package/package/corpus/rules/github-actions.md

@@ -114,6 +114,9 @@ capacity numbers into workflows or guidance.
   content the source repository's CI verified before the rollout, may carry
   `[skip ci]` once the same wrapper content has landed with CI running in one canary
   repository. Package-update bots, and any commit touching another file, keep normal CI.
+- Never put a skip token in a pull request title or an ordinary commit message: a
+  merge commit inherits the pull request title, so GitHub then runs nothing on the
+  default branch. See `cratis-engineering-release-trains`.
 - Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
   (for example `contains(github.event.comment.body, '@claude')`) so a runner only
   starts when the agent is actually addressed.
@@ -126,3 +129,9 @@ capacity numbers into workflows or guidance.
   four unintended releases on 2026-08-25.
 - Every repository's release-intent gate must accept `no-release`; a gate that only
   accepts `major`/`minor`/`patch` forces exactly that mistake.
+- Do not merge a pull request that changes `.github/workflows/` while a release Publish
+  run in the same repository has not created its tag yet. `GITHUB_TOKEN` cannot tag a
+  commit whose workflows differ from the default branch, and rerunning fails the same
+  way. Recover with the Publish `workflow_dispatch` from current main.
+- A release-verify job asserts that the GitHub release `v<version>` exists. A watch
+  picks the exact run by head SHA, never by a time window.

package/package/corpus/rules/specs.csharp.md

@@ -85,6 +85,10 @@ _service.DidNotReceive().DoSomethingElse(Arg.Any<int>());
 _handler.Handle(Arg.Any<CommandContext>()).Throws(new Exception("fail"));
 ```
 
+A change to a widely substituted interface runs the whole affected spec project,
+not one spec. Grep for `Substitute.For<IThatInterface>` to find every substitute
+that needs updating.
+
 Catch exceptions for a unit under test with `Catch.Exception`:
 
 ```csharp

package/package/corpus/skills/cratis-ci-pipeline-performance/references/build-once-and-shard.md

@@ -115,7 +115,8 @@ adding a project cannot leave it unassigned; review the list when a project is a
 
 To balance, read each shard job's median duration from the slowest-jobs table of
 `ci-timings.sh`, move a project from the longest shard to the shortest, and
-re-measure; stop when the spread is within the job start cost.
+re-measure; stop when the spread is within the job start cost. Balance by
+measured wall time, and confirm the new split on one real CI run before merging it.
 
 ## Decisions
 

package/package/corpus/skills/cratis-engineering-ci-gates/SKILL.md

@@ -42,10 +42,13 @@ before an external effect. A request to verify does not authorize a push.
    not a universal framework-specific scanner in this corpus.
 3. Prefer the repository's existing gate script. If none exists, keep a small
    local runner under `.ai-work/`, with each phase's real exit status preserved.
-   Do not substitute only the touched projects for the final gate.
+   Do not substitute only the touched projects for the final gate. The done gate
+   runs its tier's CI shards unfiltered; filters are for iterating only.
 4. **Tier 1** is the whole-solution build with CI's configuration and warning
    settings, lint/format, and every non-integration test project. For example,
-   use Release with warnings as errors when that is what CI uses.
+   use Release with warnings as errors when that is what CI uses. For a
+   dependency or analyzer bump, that exact CI Release build is the gate; a Debug
+   build is not evidence.
 5. **Tier 2** adds integration tests. The repository's tier policy decides
    whether they run locally. The default is CI-backed integration only if CI
    runs that coverage, it passes before merge, and reviewer notes say it was
@@ -53,6 +56,9 @@ before an external effect. A request to verify does not authorize a push.
 6. Name anything CI runs that cannot run locally: services, platforms, secrets
    or hosted checks. Say what ran instead and what remains unverified before
    pushing. Missing coverage is not a local pass.
+7. A change to a command, read model or query shape runs the repository's proxy
+   and API regeneration checks; never hand-edit generated files. A package bump
+   regenerates the checked-in snapshots that pin versions, in the same commit.
 
 Use affected-project checks while coding and writing specifications. Build once
 at the end: run the full local gate when the work is believed complete, not after

package/package/corpus/skills/cratis-release-notes/SKILL.md

@@ -93,6 +93,14 @@ boundary that makes a change safe to adopt. One item can follow this shape:
 That is a checklist for facts, not a template to repeat word-for-word across
 items. Use descriptive headings, meaningful links, and natural sentence rhythm.
 
+A `no-release` PR body still follows this contract. Its `(#n)` closes nothing
+because no release runs, so the issue is closed separately, and only when the
+request includes that effect; never imply automatic closing (see the issue
+section of [pull-requests.md](../../rules/pull-requests.md)).
+
+For every pull request, write the body file in a step of its own before
+`gh pr create --body-file`.
+
 ## Repair an already-published release
 
 Only when asked to fix a release that violates the contract:
@@ -134,6 +142,14 @@ dispatch the publish workflow from the current default branch with the PR's
 release notes. Re-running the stale commit does not fix this. Other 403s keep
 their original cause; do not treat every permission failure as workflow drift.
 
+Before re-running a cancelled publish, check
+`git merge-base --is-ancestor <merge-commit> <latest-release-tag>`. If it is an
+ancestor, a release already contains the change, so do not cut another version.
+The tag alone does not prove it shipped: a release can be created before its
+publishing jobs run. Confirm that the containing release's publish run completed
+every publishing job and its packages exist before reporting it shipped;
+otherwise recover that version's publishing rather than releasing again.
+
 ## Verify before handing over
 
 1. Reconcile every version, affected range, capability and API against the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.115.0",
+  "version": "7.116.1",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [