.gitignore

# >>> 8sync (managed) >>>
# Derived / machine-local — rebuilt by `8sync harness init` + codegraph. Safe to ignore:
.codegraph/
.cache/8sync/
.gs/
# Large-scope feature-planning evidence screenshots (regenerable binaries):
su-code/planning/**/evidence-*.png
# Secrets — NEVER commit:
.env
.env.*
!.env.example
# KEEP COMMITTED (do NOT add here): su-code/ (memory), AGENTS.md, CHANGELOG.md, .cursor/rules/
# Host skill mirrors (rebuilt from su-code/skills/ by `8sync harness create`):
.cursor/skills/
.zcode/skills/

# <<< 8sync <<<

# This repo dogfoods its own harness, so `8sync harness` deploys the shipped
# `assets/commands/` + `assets/extensions/` into `/.omp/` here too. That tree is
# REGENERATED OUTPUT, and tracking it guaranteed drift: the committed copy of
# 8sync-engine.ts went stale and shadowed the hardened asset. Edit the asset;
# never re-add the deployed copy. Root-anchored so `assets/` — the authoritative
# source — is unaffected. Deliberately OUTSIDE the managed block above, which
# `8sync harness init` rewrites verbatim.
/.omp/

target/
*.bak
.DS_Store
.idea/
.vscode/
Cargo.lock.bak
.codegraph/
dist/
# Project-local skill mirrors are auto-generated by `8sync skill sync` from
# ~/.omp/skills/. Don't vendor the 3rd-party skill contents — only the
# 8sync-managed force-load block in AGENTS.md / CLAUDE.md tracks which
# skills the repo expects.
su-code/skills/

reference/
# `8sync harness web` FE (derived — rebuilt by build.rs / pnpm)
web/node_modules/
web/dist/
web/*.tsbuildinfo

# npm fallback lock from web FE build (canonical: bun.lock + pnpm-lock.yaml)
web/package-lock.json

# npm (TS typecheck of shipped extensions — CI only)
node_modules/
package-lock.json