docs: drop stamps from pointer records (batch 6)

.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.

.changes/code-tidying/docs-drop-pointer-stamps-batch6-85a8a9cb.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/discovery/docs-drop-pointer-stamps-batch6-f48b7676.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/disk-hygiene/docs-drop-pointer-stamps-batch6-769afd33.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/docs-hygiene/docs-drop-pointer-stamps-batch6-6f0b292c.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/implementation/docs-drop-pointer-stamps-batch6-3c71e0a9.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/knowledge/docs-drop-pointer-stamps-batch6-dc967f54.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.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.

.changes/plugin-quality/docs-drop-pointer-stamps-batch6-9e25b417.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/review/docs-drop-pointer-stamps-batch6-b130d305.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/testing/docs-drop-pointer-stamps-batch6-d790d70d.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

.changes/work-items/docs-drop-pointer-stamps-batch6-baf6076d.md

@@ -0,0 +1,7 @@
+---
+bump: patch
+---
+
+### Changed
+
+- Pointer records no longer carry an as-of date or recheck trigger; stored values keep theirs.

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
 

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/<topic-slug>/`. 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/<topic-slug>/`. 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.

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:
-<https://raw.githubusercontent.com/melodic-software/claude-code-plugins/main/plugins/review/reference/findings-file-shape.md>.
-As of 2026-10-04; recheck when that file's "Findings-file shape" section changes. The values this
+<https://raw.githubusercontent.com/melodic-software/claude-code-plugins/main/plugins/review/reference/findings-file-shape.md>. The values this
 lens writes:
 
 - Frontmatter: `type: review-findings`, `date:` the instant of the write in ISO-8601 UTC,

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,7 +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
+  live. Recheck trigger: that README changes the component macros or the
   include path, or a host with Java can run PlantUML over a rendered block.
 - **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/`
@@ -263,8 +261,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

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,16 +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
+  live. Recheck trigger: that README changes the container macros or the
   include path, or a host with Java can run PlantUML over a rendered block.
 - **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/`
@@ -271,8 +268,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

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 "<system>"` when the invocation named one. Add `--actors "<file>"` 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,16 +203,14 @@ 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
   renderer writes, fetch
   [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
+  live. Recheck trigger: that README changes the context macros or the
   include path, or a host with Java can run PlantUML over a rendered block.
 - **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`),

plugins/architecture/skills/map-data/SKILL.md

@@ -196,8 +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
+  and [§ Supporting diagrams](https://c4model.com/diagrams#supporting-diagrams) live. Recheck trigger: C4 adds a diagram type whose subject is entities and their
   relationships.
 - **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
@@ -206,8 +205,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 +216,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 +229,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 +246,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;

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