# Files in this list are part of the GitHub repo, not the vault. ShardMind
# excludes them from `shardmind install` so the installed vault carries
# only what an Obsidian user needs. The repo still ships them so the GitHub
# landing page, contribution flow, and translated READMEs work for visitors
# who land on the repo directly.
#
# Glob semantics: gitignore-spec, minus negation (deferred to v0.2 per
# breferrari/shardmind#87). See ShardMind docs/SHARD-LAYOUT.md
# §File disposition for the three-tier model.

# Repo-meta — meaningful on GitHub, noise in a vault.
CONTRIBUTING.md
README.*.md

# Marketing media — not vault content. Patterns are explicit (not `*.png` /
# `*.gif`) so a future `.png`/`.gif` attachment landing at vault root would
# install correctly instead of being silently dropped. Update the list when
# new marketing media ship.
obsidian-mind-logo.*
obsidian-mind-demo.*

# Tests for repo-only machinery. Each of these statically imports a script
# under `.github/scripts/` or `.shardmind/hooks/` — both Tier 1 exclusions in
# the engine, which authors cannot toggle off. The import target therefore can
# never exist in an installed vault, and because the import is top-level the
# whole file fails to load (ERR_MODULE_NOT_FOUND) rather than failing a single
# assertion — so shipping them makes a user's first `npm test` fail on four
# missing modules they never asked for.
#
# They stay in the repo: CI exercises the repo-only scripts through exactly
# these tests. They just don't belong in a vault, same as CONTRIBUTING.md.
# `.claude/scripts/tests/shardmindignore.test.ts` enforces the rule generally,
# so a new test crossing the same boundary fails CI until it is listed here.
.claude/scripts/tests/manifest-check.test.ts
.claude/scripts/tests/generate-changelog.test.ts
.claude/scripts/tests/bootstrap-hook.test.ts
.claude/scripts/tests/personalize-hook.test.ts
