[jbetala7]

Fixes #1150

Summary

• gate preamble session-file tracking, pending-marker handling, and timeline logging behind telemetry != off
• move spawned-session detection behind a helper so generated SKILL.md files no longer embed the OPENCLAW_SESSION string directly
• update README wording and add regression tests around telemetry gating and generated skill output

Root cause

The preamble generator still emitted several local tracking side effects unconditionally even though telemetry: off is documented as disabling local analytics, and it embedded the OPENCLAW_SESSION env var name directly into every generated SKILL.md preamble.

Testing

• bun test test/telemetry.test.ts test/gen-skill-docs.test.ts

[jbetala7]

Rebased cleanly onto current main (post #1848) and re-pushed (head bacd6a4d); now MERGEABLE. I also tightened the scope to issue #1150 only:

• Kept the telemetry gating: session tracking (mkdir/touch/find ~/.gstack/sessions), the analytics pending-marker loop, skill-usage.jsonl writes, and gstack-timeline-log are now all behind [ "$_TEL" != "off" ] in both generate-preamble-bash.ts and generate-completion-status.ts.
• Kept the OPENCLAW_SESSION extraction into bin/gstack-spawned-session-status, so that orchestrator env-var string no longer appears in any generated SKILL.md (the scanner trigger from Session tracking and OPENCLAW_SESSION preamble not gated by telemetry config #1150).
• Dropped the earlier branch's incidental removal of the plan-mode block — that was unrelated to Session tracking and OPENCLAW_SESSION preamble not gated by telemetry config #1150, so GSTACK_PLAN_MODE detection is left exactly as on main.

Verification:

• bun test test/telemetry.test.ts test/gen-skill-docs.test.ts -> 430 pass / 0 fail
• bun test test/skill-validation.test.ts -> 329 pass
• SKILL.md regenerated via gen:skill-docs --host all; extracted preamble passes bash -n; helper verified silent without / emits SPAWNED_SESSION: true with OPENCLAW_SESSION set.

Heads-up on overlap: #1747 proposes echoing the SESSIONS count for CLAUDE.md rules to read. On current main nothing consumes the preamble's _SESSIONS (it's not exported to gstack-telemetry-log, which only runs when telemetry is on), so this gating is safe today. If #1747 lands and makes session count a non-telemetry signal, the two will need a quick reconcile — flagging so they're reviewed together.

[time-attack]

@jbetala7 Rewrite this to preserve functional context timelines for telemetry-off users, centralize session-kind detection, and update the missing generated output.

[capy-ai]

Thanks for this, @jbetala7. The fix is now on main: the OPENCLAW/session find strings the scanner flagged are no longer in SKILL.md files (moved into bin/gstack-skill-start) (already on main as of v1.91.16.0). Closing as superseded; if you still see the problem on the latest gstack, please open an issue with ./setup --status output.