docs: drop stamps from pointer records (batch 7c)

.changes/autonomy/docs-drop-pointer-stamps-batch7-bce3eefa.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/bugs/docs-drop-pointer-stamps-batch7-407dd970.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/computer-use/docs-drop-pointer-stamps-batch7-199d2db8.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/context7/docs-drop-pointer-stamps-batch7-fcb629ec.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/discipline/docs-drop-pointer-stamps-batch7-be4bea88.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/event-storming/docs-drop-pointer-stamps-batch7-63776025.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/firecrawl/docs-drop-pointer-stamps-batch7-b03af710.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/fleet/docs-drop-pointer-stamps-batch7-f8db6c03.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/mcp-tools/docs-drop-pointer-stamps-batch7-3a83cb5c.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/miro/docs-drop-pointer-stamps-batch7-159c7551.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/multi-agent/docs-drop-pointer-stamps-batch7-293834c2.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/mutation-testing/docs-drop-pointer-stamps-batch7-b546e700.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/prototype/docs-drop-pointer-stamps-batch7-78e1252c.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/rate-limit-guard/docs-drop-pointer-stamps-batch7-a4773e16.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/skill-quality/docs-drop-pointer-stamps-batch7-6506a6ed.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/user-experience/docs-drop-pointer-stamps-batch7-dbdb3321.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/visualization/docs-drop-pointer-stamps-batch7-36150c96.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/autonomy/README.md

@@ -23,8 +23,7 @@ gate is not enforced. The setup `check` reports whether `node` resolves. The hoo
 whether `node` and `jq` resolve.
 
 - **Pointer**: when checking whether a Claude Code install brings Node, fetch
-  <https://code.claude.com/docs/en/setup#install-with-npm> live. **As of**: 2026-10-11.
-  **Recheck trigger**: the setup page says the native binary ships or uses Node.
+  <https://code.claude.com/docs/en/setup#install-with-npm> live.
 
 ## Shipped capability (0.7.0)
 
@@ -148,8 +147,7 @@ marker file. The gate reads those signals itself and does not lean on the `/goal
 (pointer: when deciding whether a command hook could use that evaluator instead, fetch
 [goal: how evaluation works](https://code.claude.com/docs/en/goal#how-evaluation-works) and
 [hooks guide: prompt-based hooks](https://code.claude.com/docs/en/hooks-guide#prompt-based-hooks)
-live; as of 2026-11-03; recheck when either section changes what a command hook can trigger). The
-marker is consumed (deleted) when it authorizes a stop, one marker, one stop, so a file left in the
+live). The marker is consumed (deleted) when it authorizes a stop, one marker, one stop, so a file left in the
 checkout by a prior completed run never authorizes the stops of a later lane run. Use `/goal` for a
 single session, this gate for a standing lane.
 
@@ -180,7 +178,7 @@ settings precedence:
    session, run the arm helper from the installed plugin the same way, then pass the id as this
    plugin's `lane_stop_gate_arm_id` option through `--settings`. Read the option's settings shape
    from [settings reference: pluginConfigs](https://code.claude.com/docs/en/settings-reference#pluginconfigs)
-   live (as of 2026-11-03; recheck when that entry changes its shape).
+   live.
 3. **User `settings.json`**, located from the hook's own install path, a *persistent* enable that
    also gates interactive sessions, which defeats the default-OFF design; prefer the launcher.
 
@@ -200,22 +198,18 @@ location, so only managed settings can enable the gate there.
 
 - **Pointer**: when checking how an option value reaches a hook, fetch
   <https://code.claude.com/docs/en/plugins/manifest-reference#reference-a-saved-value> live.
-  **As of**: 2026-11-03. **Recheck trigger**: that section changes how an option value reaches a
-  hook process.
 
 It is fail-open (unreadable stdin / missing `jq` / a `SubagentStop` never trips it) and bounded
 against runaway by the `stop_hook_active` one-nudge guard plus Claude Code's own cap on
 consecutive Stop-hook continuations. It catches a graceful self-stop only: a closed laptop, a
 killed process, or `/loop` expiry emit no `Stop` event.
 
 - **Pointer**: when checking the Stop input field the guard reads, fetch
-  <https://code.claude.com/docs/en/hooks#stop-input> live. **As of**: 2026-10-11. **Recheck
-  trigger**: a Claude Code changelog entry changes the Stop hook's input fields.
+  <https://code.claude.com/docs/en/hooks#stop-input> live.
 - **Pointer**: when checking Claude Code's own cap on consecutive Stop-hook continuations and the
   setting that raises it, fetch
   [Stop hook hits the block cap](https://code.claude.com/docs/en/hooks-guide#stop-hook-hits-the-block-cap)
-  live. **As of**: 2026-10-18. **Recheck trigger**: that section changes the number of consecutive
-  blocks it allows, or renames `CLAUDE_CODE_STOP_HOOK_BLOCK_CAP`.
+  live.
 
 When the consuming repo sets `HOOK_TELEMETRY_SINK`, the gate emits one fire-and-forget envelope per
 evaluated outcome (`hook: "lane-stop-gate"`; payload contract in the marketplace's hook-telemetry

plugins/autonomy/reference/guardrails/isolation-ladder.md

@@ -13,9 +13,7 @@ document names substrate classes as marked examples only, never an instance list
   tools, hooks, and protocol-connected tool surfaces still execute on the host. An attended
   ergonomics tier, not an autonomy tier. Which level a harness's own sandbox reaches is read live:
   see the guardrail slice's
-  [sandbox rating record](../../skills/setup/context/guardrail-slice.md#harness-records-for-the-vendor-neutral-leaves)
-  (as of 2026-10-11; recheck when that record's trigger fires, or the linked heading is renamed or
-  removed).
+  [sandbox rating record](../../skills/setup/context/guardrail-slice.md#harness-records-for-the-vendor-neutral-leaves).
 - **`L2`: whole-process OS-enforced boundary with default-deny egress, credential
   protection, contained workspace host-writes, and policy nothing the run can install may
   widen.** The minimum for any unattended run, except on the

plugins/autonomy/reference/prerequisite-resolution.md

@@ -78,8 +78,7 @@ tokens"; they are not reused as probe labels.
    is a host-harness rule this contract does not restate.
    - **Pointer**: when a verdict depends on what enables a declared server, read the
      [project server enablement record](../skills/setup/context/prerequisite-resolution-slice.md#project-server-enablement)
-     and fetch the section it names live. **As of**: 2026-11-03. **Recheck trigger**: that
-     record's recheck trigger fires, or its heading is renamed or removed.
+     and fetch the section it names live.
 3. **machine-context**: CLI availability, local substrates, deterministic and per-surface. A
    result is a claim about the probed surface only, never a repo claim.
 4. **prose-context inference**: host instruction files, agent-instruction files, README are a
@@ -98,8 +97,6 @@ because this tree names no vendor. Last verified 2026-09-19, against harness ver
 - **Pointer**: when a proposal depends on which instruction files a session loads, read the
   [instruction-file loading record](../skills/setup/context/prerequisite-resolution-slice.md#instruction-file-loading)
   and fetch the sections it names live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: that record's recheck trigger fires, or its heading is renamed or removed.
 
 Probe evidence is durable per surface under the existing isolation-binding pattern. Only signals
 with no owner (CI-config presence, flag-SDK presence) gain probes owned by this contract;

plugins/autonomy/reference/routines.md

@@ -351,10 +351,8 @@ commentary, and a leaf that contradicts one is non-conforming.
   the app-control, playwright and source-control plugins plus a browser, and the network allowlist
   admits the browser download. *Basis:* the harness documentation page for cloud environments,
   section on what carries over from your setup, whose table states that a cloud session does not
-  install the plugins a repository enables in its settings. *As of:* 2026-10-04. This supersedes
-  the 2026-09-06 transfer-path record below on plugin loading. *Recheck trigger:* that table's
-  repository-settings plugin row changes, or a release note names plugin loading in cloud
-  sessions. The consumer picks the cadence (daily is a reasonable start); a
+  install the plugins a repository enables in its settings. This supersedes the transfer-path
+  record below on plugin loading. The consumer picks the cadence (daily is a reasonable start); a
   pass with no change since the last clean one skips, by the skill's own rule. No leaf under
   `routines/` is written until a consumer records a manual run of the skill.
 

plugins/autonomy/reference/runner/escalation.md

@@ -173,9 +173,6 @@ available everywhere the harness runs, a second reason it never substitutes for
 - **Pointer**: when binding either leg, read the guardrail slice's
   [escalation transports record](../../skills/setup/context/guardrail-slice.md#harness-records-for-the-vendor-neutral-leaves)
   and fetch the sections it names live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: that record's recheck trigger fires, or the linked heading is renamed or
-  removed.
 
 ### Contract-default severities
 
@@ -239,9 +236,6 @@ the two are not interchangeable.
 - **Pointer**: when adopting the interrupt shape, read the guardrail slice's
   [pause and resume record](../../skills/setup/context/guardrail-slice.md#harness-records-for-the-vendor-neutral-leaves)
   and fetch the sections it names live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: that record's recheck trigger fires, or the linked heading is renamed or
-  removed.
 
 ## Escalation telemetry
 

plugins/autonomy/reference/telemetry.md

@@ -91,9 +91,6 @@ join, because native joining does not cover every session kind the contract serv
   [Inbound trace context in headless sessions](../skills/setup/context/agent-session-telemetry.md#inbound-trace-context-in-headless-sessions)
   and [Traces stay beta](../skills/setup/context/agent-session-telemetry.md#traces-stay-beta), and
   fetch the sections they name live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: either of those records' recheck triggers fires, or either linked heading is
-  renamed or removed.
 
 ## Sink binding: out of contract
 

plugins/autonomy/skills/setup/SKILL.md

@@ -116,8 +116,7 @@ paid sinks are advisory + explicit opt-in with cost surfaced first.
 3. **Agent-session wiring (Claude Code specifics)**. Turn the session's telemetry export on with
    the variables
    [monitoring: common configuration variables](https://code.claude.com/docs/en/monitoring-usage#common-configuration-variables)
-   names, read live (as of 2026-11-03; recheck when that section renames the enable or exporter
-   variables), and for work-item-dispatched sessions set
+   names, read live, and for work-item-dispatched sessions set
    `OTEL_RESOURCE_ATTRIBUTES` carrying `autonomy.work_item.url=<canonical item URL>`. The
    slice treats spans as optional and never depends on beta span shapes. It joins on
    `autonomy.work_item.url`, never on inbound trace context; relying on native inbound-context
@@ -202,9 +201,7 @@ a watched repository's own settings cannot supply plugin options, so a repo cann
 verification. The slice proposes neither as a binding field.
 
 - **Pointer**: when checking which settings scopes plugin options are read from, fetch
-  <https://code.claude.com/docs/en/settings-reference#pluginconfigs> live. **As of**: 2026-10-11.
-  **Recheck trigger**: a Claude Code changelog entry changes the scopes `pluginConfigs` is read
-  from.
+  <https://code.claude.com/docs/en/settings-reference#pluginconfigs> live.
 
 **Layered resolution order.** Org-policy-home defaults → settings-as-code per-repo
 security binding → repo-local non-security remaps. Later layers refine earlier ones for

plugins/autonomy/skills/setup/context/agent-session-telemetry.md

@@ -15,9 +15,6 @@ for the signal events ride beside `CLAUDE_CODE_ENABLE_TELEMETRY`.
 - **Pointer**: when choosing which exporters a binding sets, fetch
   <https://code.claude.com/docs/en/monitoring-usage#events> and
   <https://code.claude.com/docs/en/monitoring-usage#code-edit-tool-decision-counter> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a Claude Code changelog entry touching the logs exporter or the code edit
-  decision counter, or either section is renamed or removed.
 
 ## Resource attributes on every datapoint and event
 
@@ -27,9 +24,6 @@ metrics on that attribute never sets `OTEL_METRICS_INCLUDE_RESOURCE_ATTRIBUTES=f
 - **Pointer**: when checking which signals carry resource attributes and what that variable
   changes, fetch <https://code.claude.com/docs/en/monitoring-usage#multi-team-organization-support>
   live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a Claude Code changelog entry touching resource attributes or
-  `OTEL_METRICS_INCLUDE_RESOURCE_ATTRIBUTES`, or that section is renamed or removed.
 
 ## Cloud session identity
 
@@ -39,9 +33,6 @@ A binding that groups or filters telemetry by cloud session keys on `ccr.session
 - **Pointer**: when attributing telemetry to a cloud or Claude Tag session, fetch the "Attribute
   telemetry to cloud sessions" section,
   <https://code.claude.com/docs/en/monitoring-usage#attribute-telemetry-to-cloud-sessions>, live.
-- **As of**: 2026-10-31
-- **Recheck trigger**: a Claude Code changelog entry touching `ccr.session.id` or cloud-session
-  attributes, or that section is renamed or removed.
 
 ## Inbound trace context in headless sessions
 
@@ -69,9 +60,6 @@ The slice treats spans as optional and never depends on beta span shapes.
 
 - **Pointer**: when a binding wires spans, fetch
   <https://code.claude.com/docs/en/monitoring-usage#traces-beta> live for the variables spans need.
-- **As of**: 2026-10-11
-- **Recheck trigger**: the page drops the beta label from that section or drops the
-  `CLAUDE_CODE_ENHANCED_TELEMETRY_BETA` flag.
 
 ## Evidence that a guardrail fired
 
@@ -85,9 +73,6 @@ rule or one hook from that event alone, and it takes no rejection evidence from
   <https://code.claude.com/docs/en/monitoring-usage#tool-decision-event>,
   <https://code.claude.com/docs/en/monitoring-usage#tool-result-event>, and
   <https://code.claude.com/docs/en/monitoring-usage#map-security-questions-to-events> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a Claude Code changelog entry touching `claude_code.tool_decision` or its
-  `source` values, or any of those sections is renamed or removed.
 
 ## GenAI mirrors on beta spans
 
@@ -96,8 +81,6 @@ records why nothing in that namespace can be pinned yet.
 
 - **Pointer**: when a binding reads span attributes, fetch
   <https://code.claude.com/docs/en/monitoring-usage#traces-beta> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: that section's span attribute tables are renamed or removed.
 
 ## Memory observability gap
 

plugins/autonomy/skills/setup/context/guardrail-slice.md

@@ -120,9 +120,6 @@ from memory.
 
 - **Pointer**: when rating it, fetch
   <https://code.claude.com/docs/en/sandboxing#what-runs-outside-the-sandbox> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a Claude Code changelog entry changes what runs outside the sandbox, or that
-  section is renamed or removed.
 
 **Escalation transports.** The
 [runner escalation leaf](../../../reference/runner/escalation.md)'s channel leg binds to a hook
@@ -133,11 +130,7 @@ that posts to an endpoint, and its push leg to the agent's own push-notification
   <https://code.claude.com/docs/en/settings-reference#agentpushnotifenabled> live for the opt-in,
   and <https://code.claude.com/docs/en/tools-reference> live for the `PushNotification` row of
   its tools table, which says where push delivery is unavailable. That table has no section
-  anchor as of this date, so the pointer names the row.
-- **As of**: 2026-10-11
-- **Recheck trigger**: the hooks page drops the HTTP hook type, the tools reference drops or
-  renames the `PushNotification` row, a release note names either surface, or either anchored
-  section is renamed or removed.
+  anchor, so the pointer names the row.
 
 **Pause and resume.** The escalation leaf's deferred mid-run interrupt would build on Claude Code's
 permission modes and on session and subagent resume, as the sections below define them.
@@ -146,6 +139,3 @@ permission modes and on session and subagent resume, as the sections below defin
   <https://code.claude.com/docs/en/permission-modes#available-modes>,
   <https://code.claude.com/docs/en/sessions#resume-a-session>, and
   <https://code.claude.com/docs/en/sub-agents#resume-subagents> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a release note names an await-human-input pause, or the resume rule changes
-  on either the sessions or the subagents page.

plugins/autonomy/skills/setup/context/prerequisite-resolution-slice.md

@@ -66,9 +66,6 @@ record holds the upstream pointer for the platform bound the
 - **Pointer**: when a proposal depends on whether a session sees `AGENTS.md`, fetch
   <https://code.claude.com/docs/en/memory#when-claude-code-reads-agents-md> and
   <https://code.claude.com/docs/en/memory#choose-which-instruction-files-load> live.
-- **As of**: 2026-10-11
-- **Recheck trigger**: a Claude Code release note names `AGENTS.md` loading or the Project
-  instructions setting, or either section is renamed or removed.
 
 ## Project server enablement
 
@@ -78,9 +75,6 @@ the config-audit surface. This record holds the upstream pointer for the enablem
 
 - **Pointer**: when deciding what enables a project server, fetch
   <https://code.claude.com/docs/en/mcp#project-server-approvals-and-workspace-trust> live.
-- **As of**: 2026-11-03
-- **Recheck trigger**: that section adds, removes or renames a setting that approves or rejects a
-  project server.
 
 ## Binding section shape