feat: wiki toggle via team config + local override (Approach C)

[jeff-r2026]

Summary

Approach C: Team Config + Local Override — The most comprehensive approach with multi-level control.

Priority chain: env var > local config > team config > default (enabled)

• Team admin can disable wiki for the entire team in teamai.yaml
• Individual users can override in ~/.teamai/config.yaml
• Env var TEAMAI_WIKI_DISABLED=1 is the highest-priority escape hatch

How to disable:

Team-level (affects all members):

# teamai.yaml
sharing:
  wiki:
    enabled: false
    disabledHint: "use external team-wiki plugin"

User-level (override team setting):

# ~/.teamai/config.yaml
wikiEnabled: false   # or true to re-enable despite team disabling

Env var (highest priority):

export TEAMAI_WIKI_DISABLED=1

When disabled:

• Wiki resources skipped during teamai pull / teamai push
• teamai-wiki builtin skill not deployed
• teamai status shows wiki status with source info (team/local/env)

Trade-offs:

Pros	Cons
Team-level enforcement	More complex implementation
User autonomy (override)	3 levels to understand
Env var escape hatch	More code to maintain
Clear status with source	Slightly more cognitive load

Backward compatibility:

• Old teamai.yaml without wiki section → enabled (default)
• Old config.yaml without wikiEnabled → follow team config
• Env var not set → follow config chain

Test plan

• resolveWikiEnabled() priority: env > local > team > default
• Team config with/without wiki section
• Local config with/without wikiEnabled
• All env var combinations tested
• Pull/push correctly filter wiki resources
• All tests pass (27 new tests + existing suite)
• TypeScript compiles cleanly

Closes #21

💡 This is 1 of 3 alternative implementations. See also:

• Approach A: Environment variable (feat/wiki-toggle-env)
• Approach B: Local config (feat/wiki-toggle-local-config)

[jeff-r2026]

Closing in favor of Approach A (#22 - env var)