diff --git a/.changes/architecture/docs-drop-pointer-stamps-batch6-6adc7e13.md b/.changes/architecture/docs-drop-pointer-stamps-batch6-6adc7e13.md new file mode 100644 index 00000000000..b6bdc3f861e --- /dev/null +++ b/.changes/architecture/docs-drop-pointer-stamps-batch6-6adc7e13.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Changed + +- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs. diff --git a/.changes/machine-health/docs-drop-pointer-stamps-batch6-a695ea69.md b/.changes/machine-health/docs-drop-pointer-stamps-batch6-a695ea69.md new file mode 100644 index 00000000000..b6bdc3f861e --- /dev/null +++ b/.changes/machine-health/docs-drop-pointer-stamps-batch6-a695ea69.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Changed + +- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs. diff --git a/plugins/architecture/reference/config.md b/plugins/architecture/reference/config.md index 41bcb9383bc..99fbaab08e8 100644 --- a/plugins/architecture/reference/config.md +++ b/plugins/architecture/reference/config.md @@ -167,9 +167,6 @@ the session is working in. [skills § Available string substitutions](https://code.claude.com/docs/en/skills#available-string-substitutions) and [skills § How injected commands run](https://code.claude.com/docs/en/skills#how-injected-commands-run) live. -- **As of**: 2026-10-11 -- **Recheck trigger**: either section changes what `${CLAUDE_SKILL_DIR}` expands to or which - working directory a skill's commands run in. ## What writes this surface diff --git a/plugins/architecture/skills/improve/SKILL.md b/plugins/architecture/skills/improve/SKILL.md index 2f83ad0d76c..df38822352b 100644 --- a/plugins/architecture/skills/improve/SKILL.md +++ b/plugins/architecture/skills/improve/SKILL.md @@ -24,8 +24,7 @@ is not a bound. - **Pointer**: when deciding how much of a command's output reaches context, fetch [tools reference § Output limits](https://code.claude.com/docs/en/tools-reference#output-limits) - live. **As of**: 2026-11-10. **Recheck trigger**: that section changes how much of a valid - result reaches context inline. + live. Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines ([gather-block convention](https://github.com/melodic-software/claude-code-plugins/blob/main/docs/conventions/gather-block/README.md#the-pre-compute-block-runs-as-one-shell-invocation), @@ -108,5 +107,5 @@ Graceful degradation: where a named step below is not available in the consuming Failure modes this lens runs into, each stated as the rule it implies. -- **The durable candidate artifact is a per-project memory-tier file, never `${CLAUDE_PLUGIN_DATA}`.** Even resolved it points at a plugin-global dir with no project dimension that collides candidates across projects. Pointer: when deciding what may live in that directory and when it is removed, fetch [plugins reference § Environment variables](https://code.claude.com/docs/en/plugins/manifest-reference#environment-variables) and [plugin components § Reference plugin paths and store data](https://code.claude.com/docs/en/plugins/components#path-variables-and-persistent-data) live. As of: 2026-11-10. Recheck trigger: either section changes the directory's lifecycle or its intended contents. The artifact lands in the memory tier, default `.work//`. A `${CLAUDE_PROJECT_DIR}/.claude/...` path is also wrong: `.claude/` generated output is reserved for observability, and an unignored artifact there leaks scan output into git. +- **The durable candidate artifact is a per-project memory-tier file, never `${CLAUDE_PLUGIN_DATA}`.** Even resolved it points at a plugin-global dir with no project dimension that collides candidates across projects. Pointer: when deciding what may live in that directory and when it is removed, fetch [plugins reference § Environment variables](https://code.claude.com/docs/en/plugins/manifest-reference#environment-variables) and [plugin components § Reference plugin paths and store data](https://code.claude.com/docs/en/plugins/components#path-variables-and-persistent-data) live. The artifact lands in the memory tier, default `.work//`. A `${CLAUDE_PROJECT_DIR}/.claude/...` path is also wrong: `.claude/` generated output is reserved for observability, and an unignored artifact there leaks scan output into git. - **Scan-agent claims are shipped only after Phase 1.5 reproduction.** Exploration subagents infer from partial reads, so a claim that a service is unused or a call path is dead can be wrong in a way a single grep settles. Any candidate headed for a `Strong` badge and any runtime-bug / dead-code claim is reproduced against the actual code before it reaches the user-facing report. The report lends every claim its authority, so an unreproduced overstatement is cheap to make and expensive to reputation. diff --git a/plugins/architecture/skills/improve/research/boundaries/README.md b/plugins/architecture/skills/improve/research/boundaries/README.md index 9b7646217f1..f34f388d4c0 100644 --- a/plugins/architecture/skills/improve/research/boundaries/README.md +++ b/plugins/architecture/skills/improve/research/boundaries/README.md @@ -59,8 +59,7 @@ That fixes what this lens can check: ## Findings rows The findings file follows review's findings-file shape: -. -As of 2026-10-04; recheck when that file's "Findings-file shape" section changes. The values this +. The values this lens writes: - Frontmatter: `type: review-findings`, `date:` the instant of the write in ISO-8601 UTC, diff --git a/plugins/architecture/skills/map-components/SKILL.md b/plugins/architecture/skills/map-components/SKILL.md index 4e8c634b05d..94547929c0e 100644 --- a/plugins/architecture/skills/map-components/SKILL.md +++ b/plugins/architecture/skills/map-components/SKILL.md @@ -243,9 +243,7 @@ a `${user_config.*}` string in a shell command), and its report line is printed. - **A component diagram is one container.** Its elements are the components inside that one container. Pointer: when deciding a component view's scope or elements, fetch [C4 component diagram § Scope](https://c4model.com/diagrams/component#scope) and - [§ Primary elements](https://c4model.com/diagrams/component#primary-elements) live. As of: - 2026-11-10. Recheck trigger: that page scopes a component diagram to something other than one - container, or names other primary elements. + [§ Primary elements](https://c4model.com/diagrams/component#primary-elements) live. - **C4-PlantUML component syntax: read against the README, never run.** The renderer writes the macros; a layer violation is a tagged `Rel` (`AddRelTag` plus `$tags`), never an `UpdateRelStyle` call. The `C4_Component` include name is our inference from the README's @@ -254,8 +252,7 @@ a `${user_config.*}` string in a shell command), and its report line is printed. [C4-PlantUML README § Component diagram](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#component-diagram) and [§ Including the C4-PlantUML library](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#including-the-c4-plantuml-library) - live. As of: 2026-11-10. Recheck trigger: that README changes the component macros or the - include path, or a host with Java can run PlantUML over a rendered block. + live. - **LikeC4 component syntax: parsed by the CLI.** The record is a probe: `likec4@1.59.4 validate` exits 0 on the golden blocks in `${CLAUDE_PLUGIN_ROOT}/lib/likec4-golden/` (`components.c4`, `components-aggregated.c4`), which `render-components.test.sh` diffs @@ -263,8 +260,7 @@ a `${user_config.*}` string in a shell command), and its report line is printed. [LikeC4 specification § Element kind](https://likec4.dev/dsl/specification/#element-kind), [model § Element](https://likec4.dev/dsl/model/#element), [views § Scoped views](https://likec4.dev/dsl/views/#scoped-views) and - [styling § Relationship](https://likec4.dev/dsl/styling/#relationship) live. As of: - 2026-11-10. Recheck trigger: any of those sections changes that syntax, or a newer `likec4` + [styling § Relationship](https://likec4.dev/dsl/styling/#relationship) live. As of: 2026-11-10. Recheck trigger: any of those sections changes that syntax, or a newer `likec4` release ships: set `LIKEC4_VALIDATE=1` when running the test to re-run the CLI. - **The record is one object per line.** A node line starts with `{"id":`. An edge line starts with `{"from":`. Any other layout exits 1 and writes diff --git a/plugins/architecture/skills/map-containers/SKILL.md b/plugins/architecture/skills/map-containers/SKILL.md index 2d1c985edfb..81feca52418 100644 --- a/plugins/architecture/skills/map-containers/SKILL.md +++ b/plugins/architecture/skills/map-containers/SKILL.md @@ -95,8 +95,7 @@ omit `--graph`. The collector reads `ProjectReference` Include attributes itself Keep the `${CLAUDE_SKILL_DIR}` anchor; [`${CLAUDE_PLUGIN_ROOT}/reference/config.md` § Script paths](${CLAUDE_PLUGIN_ROOT}/reference/config.md#script-paths) -says why. **As of**: 2026-10-11. **Recheck trigger**: that section is renamed or removed, or its -own recheck trigger fires. +says why. The record is schema_version 1 in the one-object-per-line layout the script writes. Container lines start with `{"id":`. Module lines start with `{"container":`. Edge lines start with `{"from":`. @@ -245,17 +244,14 @@ hand-written; the shared medium resolver decides the destination, with this plug and no deployment concerns. Pointer: when checking a container view's scope or elements, fetch [C4 container diagram § Scope](https://c4model.com/diagrams/container#scope), [§ Primary elements](https://c4model.com/diagrams/container#primary-elements) and - [§ Notes](https://c4model.com/diagrams/container#notes) live. As of: 2026-11-10. Recheck - trigger: the container-diagram page changes its scope, its primary elements, or moves - deployment concerns onto this diagram. + [§ Notes](https://c4model.com/diagrams/container#notes) live. - **C4-PlantUML container syntax: read against the README, never run.** The renderer writes the macros. No PlantUML run has parsed this output. Pointer: when checking the macros or the include the renderer writes, fetch [C4-PlantUML README § Container diagram](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#container-diagram) and [§ Including the C4-PlantUML library](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#including-the-c4-plantuml-library) - live. As of: 2026-11-10. Recheck trigger: that README changes the container macros or the - include path, or a host with Java can run PlantUML over a rendered block. + live. - **LikeC4 container syntax: parsed by the CLI.** The record is a probe: `likec4@1.59.4 validate` exits 0 on the golden blocks in `${CLAUDE_PLUGIN_ROOT}/lib/likec4-golden/` (`containers.c4`, `containers-stores.c4`, `containers-broker.c4`, `containers-endpoints.c4`), @@ -271,8 +267,7 @@ hand-written; the shared medium resolver decides the destination, with this plug `.search.windows.net` is labeled `Azure AI Search`. Pointer: when checking the service's endpoint form, fetch [Create a search service § Name your service](https://learn.microsoft.com/en-us/azure/search/search-create-service-portal#name-your-service) - live. As of: 2026-11-10. Recheck trigger: that section changes the endpoint form or the - service moves to another domain. The other hosts the collector labels are listed in + live. The other hosts the collector labels are listed in `store_technology`; a search service on any other host is labeled `unknown`. - **An endpoint is not an edge until it resolves.** A `localhost` URL with no `applicationUrl` on a charted deployable, a service name with no compose build context, and a URL naming an external diff --git a/plugins/architecture/skills/map-context/SKILL.md b/plugins/architecture/skills/map-context/SKILL.md index 8fb081798b3..c7597ef211f 100644 --- a/plugins/architecture/skills/map-context/SKILL.md +++ b/plugins/architecture/skills/map-context/SKILL.md @@ -97,8 +97,7 @@ skip on stderr. Reword the line without the credential and pass it again. Add `--focal ""` when the invocation named one. Add `--actors ""` only for operator-stated rows. Keep the `${CLAUDE_SKILL_DIR}` anchor; [`${CLAUDE_PLUGIN_ROOT}/reference/config.md` § Script paths](${CLAUDE_PLUGIN_ROOT}/reference/config.md#script-paths) -says why. **As of**: 2026-10-11. **Recheck trigger**: that section is renamed or removed, or its -own recheck trigger fires. +says why. The collector creates the parent directory of `--out`. Exit 1 means the record could not be written and nothing was: report the message and stop before rendering. @@ -204,8 +203,6 @@ hand-written; the shared medium resolver decides the destination, with this plug [C4 system context diagram § Scope](https://c4model.com/diagrams/system-context#scope), [§ Primary elements](https://c4model.com/diagrams/system-context#primary-elements) and [§ Supporting elements](https://c4model.com/diagrams/system-context#supporting-elements) live. - As of: 2026-11-10. Recheck trigger: that page changes the scope, the primary element, or the - supporting elements. - **C4-PlantUML context syntax: read against the README, never run.** The renderer writes the macros. The `C4_Context` include name is our inference from the README's container example. No PlantUML run has parsed this output. Pointer: when checking the macros or the include the @@ -213,8 +210,7 @@ hand-written; the shared medium resolver decides the destination, with this plug [C4-PlantUML README § System Context & System Landscape diagrams](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#system-context--system-landscape-diagrams) and [§ Including the C4-PlantUML library](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#including-the-c4-plantuml-library) - live. As of: 2026-11-10. Recheck trigger: that README changes the context macros or the - include path, or a host with Java can run PlantUML over a rendered block. + live. - **LikeC4 context syntax: parsed by the CLI.** The record is a probe: `likec4@1.59.4 validate` exits 0 on the golden block in `${CLAUDE_PLUGIN_ROOT}/lib/likec4-golden/` (`context.c4`), which `render-context.test.sh` diffs against. Pointer: when checking the syntax the renderer diff --git a/plugins/architecture/skills/map-data/SKILL.md b/plugins/architecture/skills/map-data/SKILL.md index f8cae9d38fb..f85523d4bcd 100644 --- a/plugins/architecture/skills/map-data/SKILL.md +++ b/plugins/architecture/skills/map-data/SKILL.md @@ -196,9 +196,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( skill adds no C4 dialect key and reads `diagram_dialect.data` (`mermaid` or `dbml`). Pointer: when checking which views C4 defines, fetch [C4 diagrams § Static structure diagrams](https://c4model.com/diagrams#static-structure-diagrams) - and [§ Supporting diagrams](https://c4model.com/diagrams#supporting-diagrams) live. As of: - 2026-11-10. Recheck trigger: C4 adds a diagram type whose subject is entities and their - relationships. + and [§ Supporting diagrams](https://c4model.com/diagrams#supporting-diagrams) live. - **A Prisma one-to-many is read from `@relation(fields:, references:)`.** The reader takes the scalar that `fields` names as the foreign key, and reads the relation as required when neither the relation field nor that scalar carries `?`. Pointer: when @@ -206,8 +204,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( [one-to-many relations § 1-n in the database](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/one-to-many-relations#1-n-in-the-database) and [§ Required vs optional relation fields](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/one-to-many-relations#required-vs-optional-relation-fields) - live. As of: 2026-11-10. Recheck trigger: that page stops using `fields` and `references` to - name the foreign key. + live. - **The EF reader is a stated subset of the fluent chain.** It reads `HasMany`/`HasOne`, `WithOne`/`WithMany`, `HasForeignKey`, and `IsRequired`, including the lambda form. Without `IsRequired` it takes requiredness from the foreign-key property's nullability alone, whatever @@ -218,8 +215,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( [foreign and principal keys § Non-nullable foreign key columns](https://learn.microsoft.com/en-us/ef/core/modeling/relationships/foreign-and-principal-keys#non-nullable-foreign-key-columns) and [one-to-many § Required one-to-many](https://learn.microsoft.com/en-us/ef/core/modeling/relationships/one-to-many#required-one-to-many) - live. As of: 2026-11-10. Recheck trigger: either section changes how nullability sets - requiredness, or an EF Core major release ships. The script's stderr names the property or chain that stopped a refused read; the + live. The script's stderr names the property or chain that stopped a refused read; the record's reason stays `ef-fluent-unreadable`. A declaration in the configuration file's own module is preferred over the rest of the repository. A chain outside the subset refuses the record only when EF is the winning tier. Beside a Prisma schema it is a `not-compared` row, so a @@ -232,7 +228,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( diagram names a node `module/Entity` whenever more than one module is in scope, quoted in Mermaid (`"orders/User"`). Pointer: when checking which entity names Mermaid needs quoted, fetch [entity relationship diagrams § Entities and relationships](https://mermaid.js.org/syntax/entityRelationshipDiagram.html#entities-and-relationships) - live. As of: 2026-11-10. Recheck trigger: that section changes its rule for entity names. + live. - **A required relationship does not mean the principal has at least one dependent.** The diagram uses `||--o{` for a required foreign key. That matches both Prisma and EF: the many side may be empty. The same EF page states there is no standard way to require a minimum number of @@ -249,8 +245,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( [entity relationship diagrams § Relationship syntax](https://mermaid.js.org/syntax/entityRelationshipDiagram.html#relationship-syntax) and [one-to-one relations § 1-1 in the database](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/one-to-one-relations#1-1-in-the-database) - live. As of: 2026-11-10. Recheck trigger: either section changes its markers or its uniqueness - rule. + live. - **DBML names the referenced column the declaration names.** Prisma `references: [..]` and SQL `REFERENCES t(col)` fill it, and EF `HasPrincipalKey("Col")` does. Where the declaration names none, the `Ref` becomes a `//` comment that says so, because DBML needs a column on both sides; diff --git a/plugins/architecture/skills/map-dependencies/SKILL.md b/plugins/architecture/skills/map-dependencies/SKILL.md index 790508839ec..77b6f1b76bc 100644 --- a/plugins/architecture/skills/map-dependencies/SKILL.md +++ b/plugins/architecture/skills/map-dependencies/SKILL.md @@ -256,9 +256,6 @@ The component view reads dependency-graph.json. and [MSBuild items § Create items in a project file](https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-items#create-items-in-a-project-file) live. - - **As of**: 2026-11-10 - - **Recheck trigger**: either section changes the lookup rule or the base of a relative - `Include`. - **Evidence stops at the end of the tag.** A `Version` child element on the following lines is not part of the citation. A `Version` attribute on the same tag is. - **`bin`, `obj`, `node_modules`, `vendor`, and dot-directories** other than the CI and diff --git a/plugins/architecture/skills/map-deployment/SKILL.md b/plugins/architecture/skills/map-deployment/SKILL.md index d6c75b355fd..ec9516378cb 100644 --- a/plugins/architecture/skills/map-deployment/SKILL.md +++ b/plugins/architecture/skills/map-deployment/SKILL.md @@ -311,15 +311,14 @@ its report line is printed. Procedure: every environment inside it as its own deployment environment; `--env` narrows the block to one. The diff is a table, not a picture. Pointer: when checking a deployment view's scope or elements, fetch [C4 deployment diagram § Scope](https://c4model.com/diagrams/deployment#scope) and [§ Primary and supporting elements](https://c4model.com/diagrams/deployment#primary-and-supporting-elements) - live. As of: 2026-11-10. Recheck trigger: that page changes the scope or the primary elements. + live. - **C4-PlantUML deployment syntax: read against the README, never run.** The renderer writes the macros. The `C4_Deployment` include name is our inference from the README's container example. No PlantUML run has parsed this output. `Rel` is drawn from a container to a network node its placement names, and from a Kubernetes Service or Ingress node to a container in the record's `relationships`. Pointer: when checking the macros or the include the renderer writes, fetch [C4-PlantUML README § Deployment diagram](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#deployment-diagram) and - [§ Including the C4-PlantUML library](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#including-the-c4-plantuml-library) live. As of: 2026-11-10. Recheck trigger: that README changes the deployment macros or the - include path, or a host with Java can run PlantUML over a rendered block. + [§ Including the C4-PlantUML library](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md#including-the-c4-plantuml-library) live. - **LikeC4 deployment syntax: parsed by the CLI.** The record is a probe: `likec4@1.59.4 validate` exits 0 on the golden blocks in `${CLAUDE_PLUGIN_ROOT}/lib/likec4-golden/` (`deployment-compose.c4`, `deployment-kubernetes.c4`, `deployment-ecs-shared.c4`), which @@ -366,8 +365,7 @@ its report line is printed. Procedure: [Parameters § Properties](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html#parameters-section-structure-properties) and [Dynamic references](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/dynamic-references.html#dynamic-references) - live. As of: 2026-11-10. Recheck trigger: either section changes the parameter properties or - the dynamic-reference syntax. Claim: a parameter file is either the `ParameterKey`/`ParameterValue` + live. Claim: a parameter file is either the `ParameterKey`/`ParameterValue` array or a template configuration file with a top-level `Parameters` object. Basis: . No document names a per-environment file convention, so the pairing rules above are this skill's own. @@ -378,7 +376,7 @@ its report line is printed. Procedure: [project file § Attributes](https://www.pulumi.com/docs/concepts/projects/project-file/#attributes), [§ Runtime options](https://www.pulumi.com/docs/concepts/projects/project-file/#runtime-options), and the YAML language reference's [§ Config](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#config), [§ Interpolation](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#interpolation), [§ Built-in variables](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#built-in-variables), [§ fn::toJSON](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#fntojson), - [§ fn::secret](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#fnsecret) and [§ fn::join](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#fnjoin) live. As of: 2026-11-10. Recheck trigger: any of those sections changes a key or a form. Claim: + [§ fn::secret](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#fnsecret) and [§ fn::join](https://www.pulumi.com/docs/iac/languages-sdks/yaml/yaml-language-reference/#fnjoin) live. Claim: `Pulumi..yaml` holds a `config` map keyed `[:]`, the project name is the default namespace, and an encrypted value is `secure: `. Basis: and @@ -412,17 +410,17 @@ its report line is printed. Procedure: its template, fetch [Bicep modules § Path to a module](https://learn.microsoft.com/azure/azure-resource-manager/bicep/modules#path-to-a-module) ([§ Local file](https://learn.microsoft.com/azure/azure-resource-manager/bicep/modules#local-file), [§ File in registry](https://learn.microsoft.com/azure/azure-resource-manager/bicep/modules#file-in-registry), [§ File in template spec](https://learn.microsoft.com/azure/azure-resource-manager/bicep/modules#file-in-template-spec)) and [parameter files § Define parameters file](https://learn.microsoft.com/azure/azure-resource-manager/bicep/parameter-files#define-parameters-file) and [§ Extendable parameters file](https://learn.microsoft.com/azure/azure-resource-manager/bicep/parameter-files#extendable-parameters-file) - live. As of: 2026-11-10. Recheck trigger: either page changes a path form or the `using` statement. + live. - **ARM expressions are bracketed strings.** The reader resolves only `[parameters('')]` and reads `[[` as a literal. Pointer: when checking the expression and escape rules, fetch [template expressions § Escape characters](https://learn.microsoft.com/azure/azure-resource-manager/templates/template-expressions#escape-characters) - live. As of: 2026-11-10. Recheck trigger: that section changes the escape rule. + live. - **A nested child resource carries one type segment.** The reader lists a child nested in its parent under the parent's full type plus the child's segment (`Microsoft.Web/sites/slots`). Pointer: when checking how a nested child writes its type, fetch [Bicep child resource name and type § Within parent resource](https://learn.microsoft.com/azure/azure-resource-manager/bicep/child-resource-name-type#within-parent-resource) and [ARM child resource name and type § Within parent resource](https://learn.microsoft.com/azure/azure-resource-manager/templates/child-resource-name-type#within-parent-resource) - live. As of: 2026-11-10. Recheck trigger: either section changes the single-segment rule or the nesting depth. + live. - **A slot with its own image is placed on its site's plan.** A `DOCKER|` slot places as `/` on the site's App Service plan, naming it by its full resource name, whether it is nested in the site or names it with a Bicep `parent`. **Pointer**: when deciding how a child's full @@ -430,7 +428,7 @@ its report line is printed. Procedure: [Bicep child resource name and type § Full resource name outside parent](https://learn.microsoft.com/azure/azure-resource-manager/bicep/child-resource-name-type#full-resource-name-outside-parent), [ARM child resource name and type § Outside parent resource](https://learn.microsoft.com/azure/azure-resource-manager/templates/child-resource-name-type#outside-parent-resource) and [App Service plans § Considerations for running and scaling an app](https://learn.microsoft.com/azure/app-service/overview-hosting-plans#considerations-for-running-and-scaling-an-app) - live. **As of**: 2026-11-10. **Recheck trigger**: a read of any of those sections diverges from the placement above. + live. - **Terraform values are resolved, never evaluated.** `var.X` resolves from a module call argument, then the root's tfvars files, then the variable `default`, and `${var.X}` inside a string the same way. A variable declared `sensitive = true`, or named for a credential, is redacted wherever @@ -448,12 +446,12 @@ its report line is printed. Procedure: - **Only `./` and `../` sources are local.** The reader treats only those module sources as local. Pointer: when checking how a local module path is written, fetch [module block § Local paths](https://developer.hashicorp.com/terraform/language/block/module#local-paths) - live. As of: 2026-11-10. Recheck trigger: that section changes how a local path is written. + live. - **Auto-loaded tfvars rank below the environment's file.** The reader ranks the environment's `.tfvars` above the auto-loaded tfvars files, and a variable `default` lowest. Pointer: when checking Terraform's precedence, fetch [input variables § Assign values to variables](https://developer.hashicorp.com/terraform/language/values/variables#assign-values-to-variables) - live. As of: 2026-11-10. Recheck trigger: that section changes the precedence list. + live. - **A `.tf.json` block may be an array of objects at any level.** Claim: each label level of a block (a resource's type and name) and its body may be a JSON object or a JSON array of objects, so `"resource": [{"aws_s3_bucket": {"b": {}}}]` declares the same resource as the object form. @@ -468,8 +466,7 @@ its report line is printed. Procedure: [services](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html), [`name`](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html#ECS-Type-ContainerDefinition-name) and [`serviceName`](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-serviceName) - live. **As of**: 2026-10-04. **Recheck trigger**: a read of any of those sections diverges from - the `@` placement above. + live. - **Helm reached through IaC is still Helm.** Claim: the Terraform Helm provider declares a release as `resource "helm_release"`, and the Pulumi Kubernetes provider as the type `kubernetes:helm.sh/v3:Release`. Basis: diff --git a/plugins/architecture/skills/map-events/SKILL.md b/plugins/architecture/skills/map-events/SKILL.md index 3f980fc2fad..bdeb379f264 100644 --- a/plugins/architecture/skills/map-events/SKILL.md +++ b/plugins/architecture/skills/map-events/SKILL.md @@ -133,9 +133,7 @@ hand-written; the shared medium resolver decides the destination, with this plug each call means, fetch [MassTransit consumers § Message consumers](https://masstransit.io/documentation/concepts/consumers#message-consumers), [producers § Send](https://masstransit.io/documentation/concepts/producers#send) and - [§ Publish](https://masstransit.io/documentation/concepts/producers#publish) live. As of: - 2026-11-10. Recheck trigger: the consumers page stops using `IConsumer` as the consumer - contract, or the producers page stops distinguishing publish from send. + [§ Publish](https://masstransit.io/documentation/concepts/producers#publish) live. - **Identity is the resolved type.** `Billing.Contracts.OrderPlaced` and `Shipping.Contracts.OrderPlaced` are different messages. A short name that matches two types stays unresolved rather than being joined, and a dotted name that matches no declared type diff --git a/plugins/architecture/skills/map-flow/SKILL.md b/plugins/architecture/skills/map-flow/SKILL.md index 5e6e7bf2164..b10fa777c23 100644 --- a/plugins/architecture/skills/map-flow/SKILL.md +++ b/plugins/architecture/skills/map-flow/SKILL.md @@ -52,8 +52,7 @@ This skill never writes the consumer's root instruction file or its topic doc; `--depth` defaults to 5. Keep the `${CLAUDE_SKILL_DIR}` anchor; [`${CLAUDE_PLUGIN_ROOT}/reference/config.md` § Script paths](${CLAUDE_PLUGIN_ROOT}/reference/config.md#script-paths) -says why. **As of**: 2026-10-11. **Recheck trigger**: that section is renamed or removed, or its -own recheck trigger fires. +says why. Exit 3 is a refusal whose message states the reason; nothing was written. Report the reason and stop. Do not draw a sequence from the files you can see. @@ -206,8 +205,6 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( [C4 dynamic diagram § Scope](https://c4model.com/diagrams/dynamic#scope), [§ Primary and supporting elements](https://c4model.com/diagrams/dynamic#primary-and-supporting-elements) and [C4 diagrams § Supporting diagrams](https://c4model.com/diagrams#supporting-diagrams) live. - As of: 2026-11-10. Recheck trigger: the dynamic-diagram page changes the scope or the element - rule, or the diagrams index adds or removes dynamic. - **The picture has no dialect key.** The authoring-formats convention keys only data diagrams and C4 system views, so a traced sequence stays an unkeyed mermaid `sequenceDiagram`, as `/planning:design` draws its sequence flows. The decision is recorded in @@ -234,8 +231,7 @@ option `${user_config.medium}`, or `""` when that reads empty or unsubstituted ( [controller routing § Attribute routing with HTTP verb attributes](https://learn.microsoft.com/en-us/aspnet/core/mvc/controllers/routing#attribute-routing-with-http-verb-attributes) and [minimal APIs § Routing](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis#routing) - live. As of: 2026-11-10. Recheck trigger: either section drops those attribute names or the - `Map*` route-string form. A verb prefix on the entry + live. A verb prefix on the entry (`GET /orders/{id}`) is matched against the `Http*` attribute names beside the route, or the `Map*` name. The script does not compose a class-level `[Route(...)]` with a method route; that is a limit of this adapter. diff --git a/plugins/architecture/skills/map-landscape/SKILL.md b/plugins/architecture/skills/map-landscape/SKILL.md index 82828982bbb..d649da30488 100644 --- a/plugins/architecture/skills/map-landscape/SKILL.md +++ b/plugins/architecture/skills/map-landscape/SKILL.md @@ -76,8 +76,7 @@ One call assembles both collectors into the committed record: Keep the `${CLAUDE_SKILL_DIR}` anchor; [`${CLAUDE_PLUGIN_ROOT}/reference/config.md` § Script paths](${CLAUDE_PLUGIN_ROOT}/reference/config.md#script-paths) -says why. **As of**: 2026-10-11. **Recheck trigger**: that section is renamed or removed, or its -own recheck trigger fires. +says why. `--source` and `--remote` are recorded verbatim, so a later reader can tell an explicit list from a fleet plan, and a local-only run from one that fetched. `--edges-from` is the repository whose @@ -243,8 +242,6 @@ hand-written; the shared medium resolver decides the destination, with this plug [record](https://github.com/melodic-software/claude-code-plugins/blob/main/docs/contracts/authoring-formats/README.md#why-mermaid-is-not-offered-for-the-system-key). - **Pointer**: for the landscape view Structurizr offers, see [Structurizr DSL: systemLandscape view](https://docs.structurizr.com/dsl/language#systemlandscape-view). - - **As of**: 2026-11-03 - - **Recheck trigger**: that section changes its landscape view. - **A referenced repository is not a checked-out one, and the portfolio says so.** Under the default scope only the subject repository has probed facts. Everything else is a node with edges and an `unknown` row. That is the honest answer without `--remote`, not a gap to fill by guessing. diff --git a/plugins/architecture/skills/map-landscape/reference/scope-modes.md b/plugins/architecture/skills/map-landscape/reference/scope-modes.md index ea43227ef39..cb678690b06 100644 --- a/plugins/architecture/skills/map-landscape/reference/scope-modes.md +++ b/plugins/architecture/skills/map-landscape/reference/scope-modes.md @@ -42,8 +42,7 @@ into; skip `node_modules`, `vendor`, and `.venv`; the canonical checkout is the - **Pointer**: when checking which record of that list is the main worktree, fetch [git-worktree § List output format](https://git-scm.com/docs/git-worktree#_list_output_format) - live. **As of**: 2026-11-10. **Recheck trigger**: that section changes the order or meaning of - the porcelain records. + live. ## `--remote` facts diff --git a/plugins/architecture/skills/record-decision/SKILL.md b/plugins/architecture/skills/record-decision/SKILL.md index bb1419f2a95..4b6474a5be3 100644 --- a/plugins/architecture/skills/record-decision/SKILL.md +++ b/plugins/architecture/skills/record-decision/SKILL.md @@ -22,8 +22,7 @@ is not a bound. - **Pointer**: when deciding how much of a command's output reaches context, fetch [tools reference § Output limits](https://code.claude.com/docs/en/tools-reference#output-limits) - live. **As of**: 2026-10-11. **Recheck trigger**: that section changes how much of a valid - result reaches context inline. + live. Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls, one plain command each, rather than pre-compute lines. @@ -33,8 +32,7 @@ separate body Bash calls, one plain command each, rather than pre-compute lines. [skills § How injected commands run](https://code.claude.com/docs/en/skills#how-injected-commands-run) and [worktrees § How Claude Code enforces isolation](https://code.claude.com/docs/en/worktrees#how-claude-code-enforces-isolation) - live. **As of**: 2026-10-11. **Recheck trigger**: either section changes how a skill's injected - commands run or which command shapes an isolated session refuses. + live. ## Variables @@ -176,8 +174,7 @@ records carry no such wording, say so and ask for it. place or the person declined. - **Pointer**: when choosing the surface, fetch [memory § When Claude Code reads AGENTS.md](https://code.claude.com/docs/en/memory#when-claude-code-reads-agents-md) - live. **As of**: 2026-11-10. **Recheck trigger**: that section changes when a nested - `AGENTS.md` loads. + live. Done when `git status --porcelain` shows the new record, the one retirement or partial-status change, and the line's file if it was written, and nothing else. @@ -219,8 +216,6 @@ as carrying its own license, and names the license when it declines to paste. - **Pointer**: for the repository's license terms, see `https://raw.githubusercontent.com/joelparkerhenderson/architecture-decision-record/main/LICENSE.md`. -- **As of**: 2026-09-06 -- **Recheck trigger**: that `LICENSE.md` changes, or the repository moves. Rule beside it: catalog templates are cited for the human to read, never pasted into this skill, into the reference file, or into a record. When asked to paste one, decline, name the URL and the license, diff --git a/plugins/machine-health/README.md b/plugins/machine-health/README.md index 36e7d71047e..87ea407ad0c 100644 --- a/plugins/machine-health/README.md +++ b/plugins/machine-health/README.md @@ -79,8 +79,7 @@ output base (default `Documents\MachineHealth`): `\state\` → `${CLAUDE_PLUGIN_DATA}\state\` (`history.jsonl`, `latest.json`, `approvals.json`). Old logs may stay behind or move to `${CLAUDE_PLUGIN_DATA}\logs\`. 3. `${CLAUDE_PLUGIN_DATA}` is not named `machine-health`; how Claude Code names it is in - [Environment variables](https://code.claude.com/docs/en/plugins/manifest-reference#environment-variables) - (as of 2026-10-11; recheck when that section changes how the directory name is derived). A + [Environment variables](https://code.claude.com/docs/en/plugins/manifest-reference#environment-variables). A `--plugin-dir` session was observed to name it `machine-health-inline`, which that section does not cover (basis: [CHANGELOG](CHANGELOG.md) `## [0.7.0]`, first `### Fixed` entry; as of 2026-10-11; recheck when `/machine-health:setup check` in a `--plugin-dir` session prints a path diff --git a/plugins/machine-health/skills/audit/SKILL.md b/plugins/machine-health/skills/audit/SKILL.md index b27903d7d56..3ca71199def 100644 --- a/plugins/machine-health/skills/audit/SKILL.md +++ b/plugins/machine-health/skills/audit/SKILL.md @@ -48,8 +48,6 @@ $skillRoot, $stateRoot, $reportRoot = @' - **Pointer**: skill content substitution of the plugin paths and of `${user_config.KEY}` is in [Where each variable resolves](https://code.claude.com/docs/en/plugins/manifest-reference#where-each-variable-resolves) and [Reference a saved value](https://code.claude.com/docs/en/plugins/manifest-reference#reference-a-saved-value). - **As of**: 2026-10-22. **Recheck trigger**: either section stops substituting in skill content or - starts exporting the variables to the Bash or PowerShell tool. Other runtime parameters the caller passes (via slash-command arguments, scheduled task arguments, or environment variables; the orchestrator accepts them as parameters): @@ -122,8 +120,6 @@ Routing table: - **Pointer**: the foreground command time limit is in [Tools reference, "Timeout and output limits"](https://code.claude.com/docs/en/tools-reference#timeout-and-output-limits). - **As of**: 2026-11-10. **Recheck trigger**: that section raises the foreground limit above the - audit's 15-minute runtime cap, or drops it. The orchestrator dispatches checks under per-check 90s timeouts, collects JSON results, applies the upward-only trend adjustments and the custom-check clamp, and, on non-dry runs, dispatches authorized remediations with before/after logging. 5. **Receive the structured result.** When the run reports a `run-lock` result, another audit holds the state folder and this run wrote nothing: run no discovery, write nothing, and go straight to step 8's `run-lock` sentence, skipping its report check and decision-page sentence; offer no elevated pass. When the run reports a `state-location` result, its state folder sits under a cloud sync root and nothing was written there: write no `TODO.md` and no custom check, and go to step 6. Otherwise run discovery per `reference/shared/discovery-guide.md`. Propose 1–3 OS-appropriate new checks. Straightforward read-only ones may be implemented as custom checks (script under `/scripts//checks/`, registered in the catalog overlay), except under `--scheduled`, where every proposal goes to `/TODO.md` and nothing is authored or registered; anything needing new permissions or remediation lands in `/TODO.md` for human approval. Checks broadly useful to every consumer are best contributed to the plugin itself. @@ -243,15 +239,11 @@ Upstream facts these rules rest on, read live rather than restated here: [How User Account Control works, "The consent prompt"](https://learn.microsoft.com/en-us/windows/security/application-security/application-control/user-account-control/how-it-works#the-consent-prompt); that page does not say whether the prompt shows the command line, and no elevated run has yet been observed here to show it, so these rules do not rely on the owner reading the hash at the - prompt. **As of**: 2026-10-22. **Recheck trigger**: the owner's first elevated run records what - the prompt showed, or that section starts describing the command line. + prompt. - **Pointer**: print mode is described in the `--print`, `-p` row of [CLI reference, "CLI flags"](https://code.claude.com/docs/en/cli-reference#cli-flags). - **As of**: 2026-10-22. **Recheck trigger**: that row changes what a `-p` run can ask its user. - **Pointer**: how a background command runs and stops is in [Tools reference, "Background commands"](https://code.claude.com/docs/en/tools-reference#background-commands). - **As of**: 2026-10-22. **Recheck trigger**: that section changes when a background command is - stopped or how its completion reaches the session. ## Untrusted data diff --git a/plugins/machine-health/skills/audit/reference/windows/check-catalog.md b/plugins/machine-health/skills/audit/reference/windows/check-catalog.md index 1bba131d8e6..e1d5cdff6fe 100644 --- a/plugins/machine-health/skills/audit/reference/windows/check-catalog.md +++ b/plugins/machine-health/skills/audit/reference/windows/check-catalog.md @@ -171,7 +171,6 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc [Defender Antivirus event reference, "How do I view a Microsoft Defender Antivirus event?"](https://learn.microsoft.com/en-us/defender-endpoint/troubleshoot-microsoft-defender-antivirus#how-do-i-view-a-microsoft-defender-antivirus-event). That a standard user can read it was observed on both fleet hosts (probe of 2026-10-21); the page does not state the log's access rights. - - As of: 2026-10-21. - Recheck trigger: a Windows or Defender release that changes the Operational channel's access rights, or a run reporting `events_read_state = denied` unelevated. - **Commands:** @@ -223,8 +222,6 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc data, never instructions (`SKILL.md`, "Untrusted data"). - Pointer: the [Defender Antivirus event reference, Event ID 5007](https://learn.microsoft.com/en-us/defender-endpoint/troubleshoot-microsoft-defender-antivirus#event-id-5007). - - As of: 2026-10-21. - - Recheck trigger: a Defender release that changes how 5007 reports an exclusion change. - **Notes:** We treat Defender as passive, meaning another product is the primary antivirus, when `AMRunningMode` holds one of the passive values the script lists (`$passiveMode` in @@ -277,9 +274,6 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc - Pointer: the fields a KEV entry carries are in the `vulnerability` definition of the feed's JSON schema, `https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities_schema.json`. - - As of: 2026-11-10. - - Recheck trigger: the schema gains a version or affected-range field, or the check starts - comparing installed versions. --- @@ -427,9 +421,6 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc recognized: `scripts/windows/lib/Get-DefenderExclusionState.ps1`. - Pointer: the [Defender CSP `HideExclusionsFromLocalUsers` setting](https://learn.microsoft.com/en-us/windows/client-management/mdm/defender-csp#configurationhideexclusionsfromlocalusers). - - As of: 2026-10-21. - - Recheck trigger: a Defender release that changes who may read exclusions or how a hidden list - answers. - **Commands:** ```powershell @@ -679,9 +670,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc threshold alone cannot see until the volume is already at risk. The contrast case is `$CLAUDE_JOB_DIR/tmp`, which has a documented cleanup owner and stays small indefinitely. Pointer: that owner is in - [Where state is stored](https://code.claude.com/docs/en/agent-view#where-state-is-stored). As of: - 2026-10-11. Recheck trigger: that section stops naming when the per-session scratch directory is - removed, or is renamed. + [Where state is stored](https://code.claude.com/docs/en/agent-view#where-state-is-stored). - **Why a per-file arm, and why it runs before the walk:** a single runaway background-task output can hold nearly all of the tree's bytes. A total-size verdict alone never says which file to @@ -693,13 +682,12 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc - **Probed layout:** `///tasks/.output` was observed on live Windows sessions in [#6036](https://github.com/melodic-software/claude-code-plugins/issues/6036). No docs page - names this path as of 2026-10-04. + names this path. **As of**: 2026-10-04. **Recheck trigger**: a probe finds `.output` files + outside `tasks/`. - **Pointer**: when deciding whether the running Claude Code version caps a background task's output, fetch [Interactive mode, "How backgrounding works"](https://code.claude.com/docs/en/interactive-mode#how-backgrounding-works) - live. **As of**: 2026-10-18. **Recheck trigger**: that section names where task output is - written or changes what it says about capping output size, or a probe finds `.output` files - outside `tasks/`. + live. - **Remediation:** none. `machine-health` removes nothing here; `detail.remediation_route` names `disk-hygiene:clean`, which owns removal behind its own snapshot, tier approval, and live-handle @@ -715,8 +703,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc candidates, and lists the same `tasks/*.output` level beneath it. - **Pointer**: when porting the root resolution to macOS or Linux, fetch the `CLAUDE_CODE_TMPDIR` row of [Environment variables](https://code.claude.com/docs/en/env-vars) live; it gives the - per-OS default base and the segment appended on each OS. **As of**: 2026-10-04. **Recheck - trigger**: a macOS or Linux implementation of this check is started, or that row changes. + per-OS default base and the segment appended on each OS. --- @@ -777,8 +764,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc that inherits it. What the variable does and does not block is stated in [Disable auto-updates](https://code.claude.com/docs/en/setup#disable-auto-updates); fetch it - live. **As of**: 2026-11-10. **Recheck trigger**: that section changes which update paths - `DISABLE_AUTOUPDATER` stops. Duplicate and missing PATH entries are INFO because presence is a + live. Duplicate and missing PATH entries are INFO because presence is a shape, not a verdict that the entry should be removed. --- @@ -898,9 +884,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc - **Pointer**: when deciding which attribute bits mark a file or directory that is not fully local, fetch [File Attribute Constants](https://learn.microsoft.com/en-us/windows/win32/fileio/file-attribute-constants) - live. **As of**: 2026-10-21. **Recheck trigger**: that page changes the meaning or value of - RECALL_ON_OPEN, RECALL_ON_DATA_ACCESS, PINNED or UNPINNED, or a OneDrive host shows a sync - root that carries none of those bits and is not named by a OneDrive variable. + live. - **Budget:** one 60-second budget, set in `Test-StorageTopN.ps1` with the top-15 and 10,000-file limits and enforced in `Measure-FolderSize.ps1`, covers the scan (tested before each directory and each entry) and the allocated-size pass (tested before each file). It sits under the @@ -935,7 +919,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc - **Needs admin:** no. Decision: without elevation `tasks_complete` is false and named in `admin_fields`, and every other source is read the same either way. Why: the `startup-items` row of `scripts/windows/lib/Get-ElevationMatrix.ps1`; `Complete` comes from - `scripts/windows/lib/Get-LogonTaskInventory.ps1`. **As of**: 2026-10-21. **Recheck trigger**: a + `scripts/windows/lib/Get-LogonTaskInventory.ps1`. **Recheck trigger**: a standard-token run lists as many logon tasks as an elevated run on the same host. - **Remediation:** none. The check lists; turning an entry off is the owner's action in Task Manager or Settings. @@ -960,7 +944,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc `disabled` from its task state. Decision: decode only the bytes in the table in `scripts/windows/lib/Read-StartupApproved.ps1` (its header covers the encoding) and keep every other byte `unknown` with its raw value, pinned by - `tests/windows/lib/Read-StartupApproved.Tests.ps1`. **As of**: 2026-10-21. **Recheck trigger**: a + `tests/windows/lib/Read-StartupApproved.Tests.ps1`. **Recheck trigger**: a probe ties another first byte to the state Task Manager shows, or Microsoft documents the key. - **Severity rubric:** - `UNKNOWN`: any unmuted item in the `unknown` approved state, or any location with a read @@ -983,7 +967,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc Decision: un-elevated, `prefetch_state` and `bam_state` read `denied` and are named in `admin_fields`; elevated, Prefetch and BAM add launch times. Why: the `app-last-use` row of `scripts/windows/lib/Get-ElevationMatrix.ps1`; the reads are in - `scripts/windows/lib/Get-ElevatedAppEvidence.ps1`. **As of**: 2026-10-21. **Recheck trigger**: a + `scripts/windows/lib/Get-ElevatedAppEvidence.ps1`. **Recheck trigger**: a standard-token run reads either source. - **Remediation:** none. The check never uninstalls anything. - **Commands:** @@ -1000,7 +984,6 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc Decision: `Win32_Product` is never queried; why is in the header of `scripts/windows/lib/Get-InstalledApp.ps1`, which points to the Remarks of [Win32_Product class](https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/aa394378(v=vs.85)#remarks). - **As of**: 2026-10-21. **Recheck trigger**: that Remarks warning changes or is removed. - **Evidence window:** `evidence_start` is the later of the OS install date and the profile's creation time; no launch record predates either. The window is whatever the host has, so it is reported as a date, never converted to a length of time. @@ -1018,7 +1001,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc `no-launch-recorded` means only that no launch was recorded. The record layout is decoded in `scripts/windows/lib/Read-UserAssist.ps1` (its header covers the layout); a host whose values no longer fit reads `userassist_state` `error`. - **As of**: 2026-10-21. **Recheck trigger**: `userassist_state` reads `error` on a fleet host, + **Recheck trigger**: `userassist_state` reads `error` on a fleet host, or `launched_count` reads 0 where apps are in daily use. - **Severity rubric:** - `UNKNOWN`: `userassist_state` is any read state other than `ok` or `absent` @@ -1142,8 +1125,7 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc [QueryFullProcessImageNameW](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-queryfullprocessimagenamew#parameters), [netsh http, `show servicestate` in Syntax](https://learn.microsoft.com/windows-server/administration/windows-commands/netsh-http#syntax), [Get-AuthenticodeSignature](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/get-authenticodesignature#outputs). - As of 2026-10-21. Recheck when an unelevated run starts resolving every listener, the netsh - request-queue view changes shape, or the signature status values change. + Recheck when an unelevated run starts resolving every listener. --- @@ -1188,12 +1170,12 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc differ from another host's. - Missing programs: `not-found` is trusted only when `Test-Path` wrote no error record. On a fleet host checked on 2026-10-21, every `not-found` program also failed `Get-Item` with - item-not-found, not access-denied. As of 2026-10-21. Recheck when a host run shows + item-not-found, not access-denied. Recheck when a host run shows `not-found` for a program that exists. - **Pointers:** [Get-NetFirewallRule, -PolicyStore](https://learn.microsoft.com/en-us/powershell/module/netsecurity/get-netfirewallrule#-policystore), [Get-NetFirewallPortFilter, -All](https://learn.microsoft.com/en-us/powershell/module/netsecurity/get-netfirewallportfilter#-all). - As of 2026-10-21. Recheck when the unelevated bulk port-filter read returns every filter. + Recheck when the unelevated bulk port-filter read returns every filter. --- @@ -1280,8 +1262,3 @@ All checks emit the schema in `reference/shared/output-schema.md`, and dot-sourc live; when checking which Known Folder Move policy values move a folder, fetch [Use OneDrive policies, "Silently move Windows known folders to OneDrive"](https://learn.microsoft.com/sharepoint/use-group-policy#silently-move-windows-known-folders-to-onedrive) live. -- **As of**: 2026-10-21 -- **Recheck trigger**: the System Image Backup row leaves the deprecated list or moves to the - removed-features page, wbadmin get versions stops requiring elevation, a host with a known - system image shows no Backup channel events, or the Known Folder Move section renames a value - or changes what an unset folder value moves. diff --git a/plugins/machine-health/skills/audit/reference/windows/elevation-matrix.md b/plugins/machine-health/skills/audit/reference/windows/elevation-matrix.md index c75cfadab05..f273fa81139 100644 --- a/plugins/machine-health/skills/audit/reference/windows/elevation-matrix.md +++ b/plugins/machine-health/skills/audit/reference/windows/elevation-matrix.md @@ -32,9 +32,9 @@ Residual risk, accepted: three things the standard token can write still reach t Nothing guards against these three. -- **Pointer**: how PowerShell 7 builds `PSModulePath` at startup, including the user folder a child pwsh adds back, is in [about_PSModulePath, "PowerShell 7 startup"](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_psmodulepath#powershell-7-startup). **As of**: 2026-10-26. **Recheck trigger**: that section changes the order or the sources it builds the value from. -- **Pointer**: what `CreateEnvironmentBlock` returns with no token is in [CreateEnvironmentBlock, "Parameters", `hToken`](https://learn.microsoft.com/windows/win32/api/userenv/nf-userenv-createenvironmentblock#parameters). **As of**: 2026-11-10. **Recheck trigger**: that parameter's description changes. -- **Pointer**: `FileSystemAclExtensions.CreateDirectory` creates the folder with the given security, and returns an existing folder unchanged, which is why the bootstrap names the folder randomly and checks its owner: [FileSystemAclExtensions.CreateDirectory](https://learn.microsoft.com/dotnet/api/system.io.filesystemaclextensions.createdirectory). **As of**: 2026-10-26. **Recheck trigger**: the method's summary changes what it does with an existing folder. +- **Pointer**: how PowerShell 7 builds `PSModulePath` at startup, including the user folder a child pwsh adds back, is in [about_PSModulePath, "PowerShell 7 startup"](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_psmodulepath#powershell-7-startup). +- **Pointer**: what `CreateEnvironmentBlock` returns with no token is in [CreateEnvironmentBlock, "Parameters", `hToken`](https://learn.microsoft.com/windows/win32/api/userenv/nf-userenv-createenvironmentblock#parameters). +- **Pointer**: `FileSystemAclExtensions.CreateDirectory` creates the folder with the given security, and returns an existing folder unchanged, which is why the bootstrap names the folder randomly and checks its owner: [FileSystemAclExtensions.CreateDirectory](https://learn.microsoft.com/dotnet/api/system.io.filesystemaclextensions.createdirectory). - **Pointer**: where installed plugin files live is in [Plugin loading reference, "Find plugins on disk"](https://code.claude.com/docs/en/plugins/loading#find-plugins-on-disk); the page does not say who can write there. Observed on this host on 2026-10-22: the install tree sits under the user's own profile (`\.claude\plugins\cache`), which the standard token can write. **As of**: 2026-10-22. **Recheck trigger**: that section moves the plugin cache out of the user profile or states its permissions. ## Adding a new admin-gated capability diff --git a/plugins/machine-health/skills/audit/scripts/windows/lib/Get-InstalledApp.ps1 b/plugins/machine-health/skills/audit/scripts/windows/lib/Get-InstalledApp.ps1 index be168dfd9c4..4335f09d7c0 100644 --- a/plugins/machine-health/skills/audit/scripts/windows/lib/Get-InstalledApp.ps1 +++ b/plugins/machine-health/skills/audit/scripts/windows/lib/Get-InstalledApp.ps1 @@ -20,8 +20,7 @@ and is not an update to another entry. A package counts when it is not a framework, resource or system-signed package. The Windows Installer's WMI product class is never queried: its class page warns that enumerating it starts a consistency check that verifies and repairs installed packages (Remarks of -https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/aa394378(v=vs.85)#remarks; -as of 2026-10-21, recheck when that warning changes). +https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/aa394378(v=vs.85)#remarks). ReadState is ok when every source read; otherwise the first failing source's state, with the apps the other sources returned. diff --git a/plugins/machine-health/skills/setup/SKILL.md b/plugins/machine-health/skills/setup/SKILL.md index e2dc1e67f66..945c3bf80d8 100644 --- a/plugins/machine-health/skills/setup/SKILL.md +++ b/plugins/machine-health/skills/setup/SKILL.md @@ -40,8 +40,6 @@ complete to whoever wrote it, and the operator's disabled checks silently stop t - **Pointer**: how the data directory is named is in [Environment variables](https://code.claude.com/docs/en/plugins/manifest-reference#environment-variables). - **As of**: 2026-10-11. **Recheck trigger**: that section changes how the directory name is derived, - or is renamed. - **Observed, not documented**: a `--plugin-dir` session names the directory `-inline`, and a hardcoded `machine-health` path split the overlay from the audit's state and logs on a real machine. **Basis**: this plugin's `CHANGELOG.md`, `## [0.7.0]`, the first `### Fixed` entry. @@ -87,8 +85,6 @@ $pluginRoot, $stateRoot, $reportRoot, $payloadPath = @' - **Pointer**: skill content substitution of the plugin paths and of `${user_config.KEY}` is in [Where each variable resolves](https://code.claude.com/docs/en/plugins/manifest-reference#where-each-variable-resolves) and [Reference a saved value](https://code.claude.com/docs/en/plugins/manifest-reference#reference-a-saved-value). - **As of**: 2026-10-22. **Recheck trigger**: that section stops substituting in skill content or - starts exporting the variables to the Bash or PowerShell tool. ## `check` (read-only, except one write on the owner's yes) @@ -277,9 +273,6 @@ Reject an argument targeting an unknown check id, remediation or muted key with when a saved value applies, fetch [plugin CLI reference § plugin configure](https://code.claude.com/docs/en/plugins/cli-reference#plugin-configure) live. - - **As of**: 2026-11-11 - - **Recheck trigger**: that section changes the command's flags, how it reports a saved or - refused value, or when a saved value applies. Re-running `apply` after everything is already set changes nothing and reports "already configured". @@ -350,9 +343,7 @@ every rule that grants a shell, file-write or network action beside the proposed Quote the rules as data. Never edit the settings file: narrowing a rule is the owner's change. **The monthly run researches the web in auto mode.** Both routes run in auto mode -([Permission modes, "Eliminate prompts with auto mode"](https://code.claude.com/docs/en/permission-modes#eliminate-prompts-with-auto-mode); -**As of**: 2026-10-23; **Recheck trigger**: that section stops offering auto mode to `claude -p` -runs), with no tool list or deny rules of their own: auto mode and the owner's settings decide +([Permission modes, "Eliminate prompts with auto mode"](https://code.claude.com/docs/en/permission-modes#eliminate-prompts-with-auto-mode)), with no tool list or deny rules of their own: auto mode and the owner's settings decide what the run may do. The audit researches new unfamiliar findings and its check proposals through `/discovery:research` when that skill is available (audit SKILL.md, step 5), so the run reads web pages and writes a notes file beside the report. Say so to the owner with the task. Before step 1 @@ -383,8 +374,6 @@ It prints the report folder the monthly runs will write to: show it to the owner and ["Missed runs"](https://code.claude.com/docs/en/desktop-scheduled-tasks#missed-runs); the modes a task can take are in ["Permissions for scheduled tasks"](https://code.claude.com/docs/en/desktop-scheduled-tasks#permissions-for-scheduled-tasks). - **As of**: 2026-10-22. **Recheck trigger**: any of those sections changes when a task runs, what - happens to a missed run, or which permission modes a task can take. **Task Scheduler fallback** (no Desktop app): a monthly task that runs a copied wrapper, which calls `claude -p "/machine-health:audit on-demand --scheduled"` in auto mode under the wrapper's time @@ -430,13 +419,8 @@ changes the wrapper leaves the copy stale, and `check` step 6 FAILs it and offer - **Pointer**: print mode and the `--permission-mode` and `--bare` flags are in [CLI reference, "CLI flags"](https://code.claude.com/docs/en/cli-reference#cli-flags); the wrapper never passes `--bare`. - **As of**: 2026-11-10. **Recheck trigger**: that row changes what `--bare` loads, or a - [Claude Code CHANGELOG](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md) entry - makes `--bare` the `-p` default or adds a `--no-bare`-style flag. - **Pointer**: Git Bash's rewriting of slash-led arguments is in [MSYS2, "Filesystem Paths"](https://www.msys2.org/docs/filesystem-paths/#automatic-unix-windows-path-conversion). - **As of**: 2026-10-22. **Recheck trigger**: that section stops converting slash-led arguments - passed to a native program. ## Output