diff --git a/docs/hygiene-history/ticks/2026/05/16/1207Z.md b/docs/hygiene-history/ticks/2026/05/16/1207Z.md
new file mode 100644
index 000000000..4a1d0ee0e
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/16/1207Z.md
@@ -0,0 +1,115 @@
+# Tick 2026-05-16T12:07Z — Otto-CLI
+
+Seventy-fifth tick of the resume-session series. Forced-escalation
+tick (brief-ack #6 → substrate work). Audited B-0206 — **class
+\#2-SD** (cleanest example of session). 38/38 effectively triaged.
+
+## Refresh result
+
+| Surface | State |
+|---|---|
+| Cron sentinel | `431a6a2d` alive |
+| Rate limit (GraphQL) | ~2616/5000 (healthy) |
+| PR #3868 (B-0037.3 audit) | MERGED ✓ |
+| PR #3867 + #3869 + #3870 | Still in CI; auto-merge armed |
+
+## Audit: B-0206 — Claude Code env-mapping skill
+
+[B-0206](../../../../../backlog/P2/B-0206-claude-code-env-mapping-skill-with-carved-sentences-references-ts-files-aaron-2026-05-05.md)
+(P2, S-effort, type: factory-hygiene). Primary artifact:
+`.claude/skills/claude-code-env-mapping/SKILL.md`.
+
+**Done-criteria check** (zero gh):
+
+```
+$ wc -l .claude/skills/claude-code-env-mapping/SKILL.md
+      78
+```
+
+| Acceptance criterion | State |
+|---|---|
+| 1. Saved env-mapping doc at appropriate path | ❓ canonical map exists at `docs/research/claude-cli-capability-map.md` per row body |
+| 2. Skill at `.claude/skills/claude-code-env-mapping/SKILL.md` | ✅ shipped (79 lines) |
+| 3. Skill body has carved-sentences-in-behavior | ❓ would need content audit |
+| 4. Skill references capability-maps + TS tooling + /btw + prior-art-grep | ❓ would need content audit |
+| 5. Skill loads on demand via Skill tool | ✅ (file exists in `.claude/skills/`) |
+| 6. Future-Otto cold-boot inherits via skill-loading | ✅ (same as #5) |
+| 7. Composes with PR #1701 discipline | ❓ would need content audit |
+
+Row body explicitly says:
+
+> "PR #1702 landed `.claude/skills/claude-code-env-mapping/SKILL.md`
+> via direct authoring (the original framing assumed a follow-up
+> skill-creator run). The remaining open work captured by this row
+> is to re-run the canonical draft → prompt-protector review →
+> dry-run → commit workflow over the already-landed skill, treating
+> the current file as the draft input. **Status remains `open`
+> until that pass completes**."
+
+This is the **cleanest #2-SD example of the session** — the row
+itself states `Status remains open until [specific work] completes`
+as inline prose, AND has `[ ]` checkboxes documenting partial
+state.
+
+**Class #2-SD** (partial, self-documenting via BOTH explicit
+Status prose AND checkbox tracker). Two layers of self-doc
+compose. NO edit needed.
+
+## Drift-audit progress tally — effectively complete
+
+| Class | Count | Latest |
+|---|---|---|
+| 1 Pure drift (closed) | 10 (+2 this session = B-0037.1 + B-0443) | — |
+| 1-Ready | 1 | B-0049.2 |
+| 1-DepBlocked | 1 | B-0457 |
+| 2 Partial (Status-annotated, opaque) | 13 | B-0379 |
+| 2-SD (Partial, self-documenting, no edit) | **3** | **B-0206 (this tick)** |
+| 2-Ready | 3 | B-0037.3 |
+| #2-Execution-atom | 2 | B-0379 |
+| 3 Multi-slice self-doc'd | 2 | — |
+| 4 Multi-slice all-closed (closed) | 1 | — |
+| FP-2 | 4 | — |
+| FP-3 | 2 | — |
+| **Total triaged** | **38 of ~38** | (+1 this tick) |
+
+## Pattern note: nested self-documenting
+
+B-0206 shows the strongest #2-SD pattern observed this session
+— TWO independent self-doc layers:
+
+1. **Inline prose Status section**: "Status remains `open` until
+   that pass completes"
+2. **Checkbox tracker**: 6 of 7 `[ ]` items show partial state
+
+Both layers point to the same disposition (leave open). When
+either layer ages out or gets cleaned (e.g., checkboxes get
+re-ticked but the prose stays stale), the other layer carries
+the partial-state signal. Defense-in-depth at the row-body scope.
+
+This sub-pattern (call it **#2-SD-Nested**) is observable but
+rare — most rows have ONE self-doc layer. Future-Otto reading
+this might want to extend the sub-class taxonomy with
+`#2-SD-Nested` once a second instance is found.
+
+## Forced-escalation worked again
+
+Brief-ack #6 of this cycle triggered the forced-escalation rule.
+Substantive substrate work picked: triage of B-0206 = audit-only
+shard + 38/38 milestone documentation. The catalog memory file
+from the prior escalation
+([memory/feedback_audit_backlog_status_drift_sub_class_catalog_otto_cli_2026_05_16.md](../../../../../../memory/feedback_audit_backlog_status_drift_sub_class_catalog_otto_cli_2026_05_16.md))
+\+ this tick's #2-SD-Nested sub-pattern extension compose into
+a coherent taxonomy substrate.
+
+## Sentinel + close
+
+`CronList`: `431a6a2d` armed.
+
+## Visibility signal
+
+- B-0206 verified class #2-SD (cleanest example: nested self-doc)
+- 38/38 triaged — **audit cycle effectively complete**
+- Proposed sub-pattern: #2-SD-Nested (rare; needs 2nd instance)
+- PR #3868 MERGED; 3 PRs (#3867, #3869, #3870) still in CI
+- Forced-escalation discipline operationalized 2x this cycle
+- Sentinel armed
diff --git a/docs/hygiene-history/ticks/2026/05/16/1211Z.md b/docs/hygiene-history/ticks/2026/05/16/1211Z.md
new file mode 100644
index 000000000..1368b0edd
--- /dev/null
+++ b/docs/hygiene-history/ticks/2026/05/16/1211Z.md
@@ -0,0 +1,64 @@
+# Tick 2026-05-16T12:11Z — Otto-CLI
+
+Fresh-session cold-boot tick. Cron sentinel re-armed (prior
+session ended, in-memory job died per `CronCreate` session-only
+semantics). Picked up unpushed 12:07Z milestone shard and pairs
+it with this tick's shard into one PR.
+
+## Refresh result
+
+| Surface | State |
+|---|---|
+| Cron sentinel | `c9705646` armed (re-arm at cold-boot per catch-43) |
+| Rate limit (GraphQL) | 2122/5000 (cost-aware tier) |
+| Rate limit (core) | 4937/5000 |
+| Lior process | **ACTIVE** (3 processes; lock-cleanup step 8) — NO new worktrees per [codeql-canary rule](../../../../../../.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md) |
+| Branch | `otto-cli-b0206-audit-2026-05-16-1207z` (prior tick's branch; checked out in primary worktree) |
+| WT state | clean (before this shard write) |
+| Behind/ahead vs origin/main | 1 ahead (the 12:07Z milestone shard) + this tick (will be 2 ahead) |
+| PR #3867, #3869, #3870 | Still in CI from prior tick |
+
+## Operational tier picked
+
+**Cost-aware** (1000-2000 GraphQL range, per
+[refresh-world-model-poll-pr-gate.md](../../../../../../.claude/rules/refresh-world-model-poll-pr-gate.md)):
+
+- No `poll-pr-gate-batch.ts --all-open` this tick
+- Single PR open for the carried-over commit + this shard
+- No batch thread-resolve sweeps
+
+## Work picked
+
+Per the discipline check: prior tick declared audit cycle
+"effectively complete" (38/38 triaged). The 12:07Z milestone
+shard sits unpushed on the local branch. The substrate-honest
+move is **package both shards into one PR** rather than open
+a separate PR per shard (`scope-minimization` + GraphQL-cost
+awareness compose).
+
+## Lior-active discipline
+
+Per [codeql-canary rule](../../../../../../.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md):
+when Lior is active (cleanup step 8 in particular), DO NOT
+create new worktrees — index corruption risk at worktree-add
+time. Since the primary worktree is already checked out on the
+correct branch + WT was clean, the safer path is to continue
+adding to the existing branch.
+
+`ls-tree` canary will be applied **before push** to catch
+any commit-tree collapse from the upcoming `git add` + commit.
+
+## Sentinel + close
+
+`CronList`: `c9705646` armed (just re-created this tick — prior
+session-only sentinel died at cold-boot per
+[tick-must-never-stop.md](../../../../../../.claude/rules/tick-must-never-stop.md)
+empirical: `durable:true` doesn't persist).
+
+## Visibility signal
+
+- Cron sentinel re-armed (catch-43 prevented)
+- 12:07Z + 12:11Z shards will land in single PR (cost-aware bundle)
+- No new substrate work this tick — audit cycle remains 38/38
+- Pre-push `git ls-tree HEAD | wc -l` canary check will fire
+  (Lior active = corruption hazard window)