fix(core): correct commits path, fix typo, and remove stray code fence

## Why
`core/AGENTS.md` referenced a non-existent path (`~/.claude/core/commits.md`)
instead of the correct `~/.claude/core/instructions/commits.md`, and contained a
typo ("commiting" → "committing"). `core/instructions/commits.md` was wrapped in
an erroneous markdown code fence that caused agents reading the file to see it as
a raw text block rather than a live template with usable HTML comment sections.

## Impact
Agents following the content index in AGENTS.md will now resolve the correct path
for commit conventions. The commits template is now properly structured so its
comment-gated sections render as intended.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/settings.json

@@ -3,6 +3,7 @@
     "PreToolUse": []
   },
   "enabledPlugins": {
-    "kyberforge@holocron": true
+    "kyberforge@holocron": true,
+    "bin@holocron": true
   }
 }

.mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "obsidian": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "@bitbonsai/mcpvault@latest",
+        "docs/"
+      ]
+    }
+  }
+}

core/AGENTS.md

@@ -24,4 +24,4 @@ Read these files on demand:
 - **Coding conventions** (`~/.claude/core/instructions/coding.md`) — when writing, editing, or reviewing code
 - **Git conventions** (`~/.claude/core/instructions/git.md`) — when doing git operations
 - **Testing conventions** (`~/.claude/core/instructions/testing.md`) — when writing or running tests
-- **Workflows / agents / prompts** (`~/.claude/core/`) — read from here when invoked
+- **Git Commit conventions** (`~/.claude/core/instructions/commits.md`) — when committing changes

core/instructions/commits.md

@@ -0,0 +1,78 @@
+<!--
+<type>(<scope>): <concise summary>
+Required.
+
+Purpose:
+- Quickly communicates the intent when scanning `git log`.
+- Follow Conventional Commits for consistency and tooling.
+- Describe the intended outcome, not the implementation.
+
+Examples:
+feat(auth): support OAuth device flow
+fix(cache): prevent stale session reuse
+refactor(api): simplify request validation
+-->
+
+## Why
+<!--
+Explain why this change exists.
+
+This is the most valuable part of the commit because the code diff
+already shows WHAT changed. Future maintainers (human or AI) often
+need to understand WHY the change was made.
+
+Include, where applicable:
+- Problem being solved
+- User or business need
+- Bug or root cause
+- Important context that is not visible in the code
+
+Omit if the reason is immediately obvious.
+-->
+
+## Implementation Notes
+<!--
+Capture decisions that are difficult to infer from the code.
+
+Useful information includes:
+- Why this approach was chosen
+- Important assumptions or invariants
+- Constraints imposed by external systems
+- Tradeoffs or intentional compromises
+- Non-obvious implementation details
+- Workarounds or temporary solutions
+
+Do NOT describe the diff ("renamed X", "added Y", etc.).
+The code already documents that.
+Omit if there is nothing worth preserving.
+-->
+
+## Impact
+<!--
+Document effects that future developers should know.
+
+Examples:
+- Behavior changes
+- Breaking changes
+- Performance implications
+- Security considerations
+- Migration or deployment requirements
+- Compatibility concerns
+- Follow-up work or known limitations
+
+Omit if there are no noteworthy impacts.
+-->
+
+---
+# References
+<!-- Git Trailers:  Structured metadata for traceability and tooling. Use only the trailers that apply. -->
+
+Fixes:
+Refs:
+ADR:
+RFC:
+Design:
+Co-authored-by:
+Reviewed-by:
+Signed-off-by:
+BREAKING CHANGE:

core/instructions/git.md

@@ -1,10 +1,13 @@
 # Git conventions
 
 - Never skip hooks with `--no-verify`. Hooks are the automated QA gate; bypassing them breaks the pipeline.
-- Never force-push main or master.
+- Never force-push `main` or `master`.
-- Commit messages explain why, not what. Written for both humans and changelog generators.
+- Keep commits atomic. Each commit should represent one logical, independently reviewable and reversible change.
+- Ensure every commit leaves the repository in a working state (buildable/testable where practical).
+- Commit messages explain **why**, not **what**. The diff already documents what changed.
 - Never commit secrets, credentials, or environment-specific config.
-- Use conventional commits: `feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, `test:`
+- Use Conventional Commits (`feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, `test:`, etc.).
+- Reference related issues, ADRs or design documents using Git trailers when applicable.
 
 ## Submodules