mirror of
https://github.com/gastownhall/beads.git
synced 2026-09-14 20:17:24 +08:00
CI Bot
a82e688953
Both files had their Last reviewed markers refreshed today without the content gaps being closed, so the freshness signal is currently green on two docs that are missing real material. azure-devops.md — `ado.reconcile_interval` is undocumented. It is real, user-tunable config (internal/ado/reconcile.go, default 10) setting how many syncs pass between automatic reconciliation scans, and the doc already documents the `--reconcile` flag that forces one. Adds a Reconciliation section, and notes that `ado.syncs_since_reconcile` is beads' own counter rather than a setting. otel-data-model.md — claims a complete schema but lists 7 of 111 storage spans, so the issueops role surface is invisible to anyone instrumenting from it. Rather than 100+ prose sections that would drift again, state the rule the code follows — span name is "storage." + operation name, which is also the db.operation attribute (InstrumentedStorage.op) — and inventory both families: 72 direct storage.<Method> spans and 39 storage.<Role>.<Method> spans. Also records why the families do not double-count: the role decorators wrap the UNINSTRUMENTED store (IssueLifecycle calls Unwrap() before wrapping), so one logical operation emits one span on either path and the counters stay comparable. No behaviour change; documentation catching up to the code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>