CLAUDE.md ยท diff

git:20260612.683e413 to git:20260625.15b55d6

8 added, 0 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

# Claude Code Instructions
Use PUDO as the operating workflow for this repository: Plan -> Understand -> Develop -> Optimize.
This root file is the Claude Code memory bridge. It keeps the README integration link valid and points Claude to the fuller Claude-specific guide in `claude/CLAUDE.md`.
## Required Workflow
- Plan before implementation for non-trivial work.
- Inspect relevant files before editing.
- Keep patches small and scoped.
- Preserve existing user changes.
- Run relevant checks, or state why checks were skipped.
- Use quality gates before handoff or release.
## Model-Specific Notes
### Claude Fable 5
When running on Fable 5 (model: `claude-fable-5`), leverage the 1M token context for:
- Large refactors spanning 10+ files โ€” include all relevant files in a single context pack
- Long-running autonomous tasks โ€” use session handoff for checkpoints across multi-hour work
- Self-correction loops โ€” Fable 5 can refine its own work without user intervention
## Repository References
- Core agent workflow: `AGENTS.md`
- Claude-specific guide: `claude/CLAUDE.md`
- Quality gates: `quality/quality-gates.md`
- QC checklists: `quality/qc-checklists.md`
- AI output review: `quality/ai-output-review.md`
- Edge cases: `quality/edge-cases/general.md`
## Avoid
- Guessing APIs, paths, or file contents.
- Rewriting unrelated files.
- Adding dependencies without justification.
- Removing or weakening tests without approval.
- Hiding failed or skipped verification.
+ ## Release & Package Quality
+
+ - **Maintain npm Package:** Evolve the repository while keeping it fully functional as an npm package for the MCP Server.
+ - **Git Branch Workflow:** Never work directly on default branch; use dedicated feature branches (e.g. `feature/...`).
+ - **Commit Strategy:** Stage only one file at a time and commit it with a Conventional Commit.
+ - **Semantic Versioning & Changelog:** Bump versions using [VERSIONING.md](release/VERSIONING.md) and update `CHANGELOG.md` using [CHANGELOG_TEMPLATE.md](release/CHANGELOG_TEMPLATE.md). Follow [RELEASE_CHECKLIST.md](release/RELEASE_CHECKLIST.md) and [PUBLISH_NPM.md](release/PUBLISH_NPM.md).
+
+