chore: kanban template

.gitignore

@@ -0,0 +1,49 @@
+node_modules
+dist
+.next
+.vite
+.tanstack
+.deploy/
+.wrangler/
+.pikku-runtime/
+
+# Local dev SQLite database (regenerated via `pikku db migrate`)
+packages/functions/.pikku/dev.db
+packages/functions/.pikku/dev.db-*
+
+# Locally instantiated apps. Real projects commit these; the template
+# repo never ships an instantiated user app.
+!apps/fabric-design/
+
+# Generated by @pikku/cli — regenerated on `pikku all`.
+# Ignore the contents (not the directory) so negation below can whitelist
+# the `api.gen.ts` stub that keeps the skeleton compilable pre-`pikku all`.
+packages/functions/src/pikku/*
+packages/functions/.pikku/*
+!packages/functions/.pikku/client
+packages/functions/.pikku/client/*
+!packages/functions/.pikku/client/api.gen.ts
+packages/functions/.pikku-runtime/
+# Compiled .js siblings of the checked-in scaffold .gen.ts files.
+packages/functions/src/scaffold/*.gen.js
+
+# Yarn — commit the root lockfile; ignore PnP/cache and generated per-unit lockfiles
+.yarn/
+.pnp.*
+yarn.lock
+!/yarn.lock
+
+# pikku deploy plan output — regenerated by the deploy container
+packages/functions/.deploy/
+
+# OpenCode config, skills, tools + templates — all written by the Fabric dev
+# machine at startup, never committed to the project repo.
+.opencode/
+
+# Vendored pikku tarballs — a temporary packaging hack. The stable-named
+# tarballs (e.g. vendor/pikku-core.tgz) are committed: package.json resolves
+# `file:./vendor/*.tgz` against them and project creation seeds new repos from
+# them, so they must stay tracked. The dev machine's sync_vendor_packages also
+# drops versioned copies (e.g. vendor/pikku-core-0.12.20.tgz) at boot — ignore
+# only those so they don't dirty the tree and block fast-forward pulls.
+vendor/*-[0-9]*.tgz