Harness-level anomaly observed 2026-08-15, session a86db903 (Claude Code remote/cloud, this repo): the SessionStart bootstrap reported "plugins 65 enabled, 65 newly installed", yet the user's first message /docs-hygiene:audit-derivability returned Unknown command: /docs-hygiene:audit-derivability (local-command-stdout). Later in the same session the skill listing included the full plugin skill set, and other plugin machinery (hooks) ran from installed copies throughout. Workaround used in-session: read the SKILL.md from the repo working tree and follow it manually — which also silently bypasses skill-load string substitutions (${CLAUDE_EFFORT} etc.; see the self-detection clause added to session-flow:orchestrate in #2695).
Hypothesis (unverified): registration/timing gap between cloud-bootstrap plugin install and the slash-command registry for the session's first turn. No official doc describes registration timing for cloud-bootstrap installs; the cause could not be verified from inside the plugin (plugin-quality audit packet docs-hygiene-audit-derivability/20260815T104849Z, "Environmental anomaly" section — explicitly not remediable in any plugin here).
Suggested handling:
- Track occurrences via
/claude-ops:known-issues and reproduce on a fresh cloud session (does the first turn always miss bootstrap-installed commands?).
- If reproducible, report upstream (anthropics/claude-code) with the bootstrap log + first-turn transcript as evidence.
- Optional mitigation in this repo's cloud bootstrap docs: note that first-turn slash invocations of just-installed plugins may need a retry or direct-file fallback.
Harness-level anomaly observed 2026-08-15, session a86db903 (Claude Code remote/cloud, this repo): the SessionStart bootstrap reported "plugins 65 enabled, 65 newly installed", yet the user's first message
/docs-hygiene:audit-derivabilityreturnedUnknown command: /docs-hygiene:audit-derivability(local-command-stdout). Later in the same session the skill listing included the full plugin skill set, and other plugin machinery (hooks) ran from installed copies throughout. Workaround used in-session: read the SKILL.md from the repo working tree and follow it manually — which also silently bypasses skill-load string substitutions (${CLAUDE_EFFORT}etc.; see the self-detection clause added to session-flow:orchestrate in #2695).Hypothesis (unverified): registration/timing gap between cloud-bootstrap plugin install and the slash-command registry for the session's first turn. No official doc describes registration timing for cloud-bootstrap installs; the cause could not be verified from inside the plugin (plugin-quality audit packet
docs-hygiene-audit-derivability/20260815T104849Z, "Environmental anomaly" section — explicitly not remediable in any plugin here).Suggested handling:
/claude-ops:known-issuesand reproduce on a fresh cloud session (does the first turn always miss bootstrap-installed commands?).