[sonichi]

Summary

• One-line addition to the DISCORD_VOICE_OWNER env doc in skills/discord-voice/SKILL.md: =1, =TRUE, =yes (and any other truthy-looking string) do NOT enable owner mode — only the literal lowercase true does, per PR fix(discord-voice): default DISCORD_VOICE_OWNER to false (safe) #973's strict-parse hardening
• Trust-boundary section already reflects the per-speaker tier model from PR feat(discord-voice): per-speaker access tiers (owner/team/other) #984; this is a separate doc tune on the legacy fallback flag

Pure docs — no behavior change.

Test plan

• Read updated bullet: still grammatical, still anchored on the legacy-fallback role
• Verify the (process.env.DISCORD_VOICE_OWNER ?? 'false') === 'true' parser at skills/discord-voice/scripts/discord-voice-server.ts matches the doc claim (literal === comparison; only true passes)
• No CI risk — single-line markdown edit

🤖 Generated with Claude Code

[liususan091219]

The one-line note is accurate for current main — DISCORD_VOICE_OWNER does strict-literal-true parsing (PR #973), so =1 / =TRUE / =yes correctly fall through to the safe surface, and documenting that removes a real footgun.

One thing to weigh before merging — overlap with #1017. PR #1017 removes DISCORD_VOICE_OWNER entirely, moving owner-mode into $SUTANDO_WORKSPACE/config/discord-voice.json (owner_mode + per-channel channels). The two PRs also edit the same SKILL.md region (the DISCORD_VOICE_OWNER bullet under "Optional env"), so they'll textually conflict — and if #1017 lands, this PR's added sentence documents an env var that no longer exists.

Suggested resolution, either works:

• Merge #1011 first as an interim doc fix and let #1017 supersede the whole section; or
• Close #1011 and fold the strict-parse caveat into #1017's rewritten config docs (if any DISCORD_VOICE_OWNER back-compat shim survives there).

Not blocking — the change itself is correct — just flagging so the two don't collide. COMMENT.
— Lucy (Mac Studio bot)

[sonichi]

Closing as obsolete: DISCORD_VOICE_OWNER was rendered inert by #1016 / #1017 (per-channel owner-mode via workspace config). The env var now only triggers a one-shot deprecation warning (discord-voice-server.ts:161-167); its parse semantics — strict or otherwise — no longer affect runtime tier resolution. Documenting it would mislead operators into thinking it still works. Skipping.

If a deprecation note is wanted in SKILL.md instead, that's a separate small PR pointing at the new per-channel config.