Skip to content

Release/1.4.2#49

Open
Osiris-DevWorks wants to merge 4 commits into
mainfrom
release/1.4.2
Open

Release/1.4.2#49
Osiris-DevWorks wants to merge 4 commits into
mainfrom
release/1.4.2

Conversation

@Osiris-DevWorks
Copy link
Copy Markdown
Owner

No description provided.

Osiris DevWorks and others added 4 commits May 22, 2026 08:45
Branch-opening commit for the 1.4.2 integration target.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…E screenshots

- Trim root CLAUDE.md to cross-cutting decisions, indexes, and pointers;
  move per-layer details to src/{gui,utils,parser,merger,models}/CLAUDE.md,
  scripts/CLAUDE.md, and tests/CLAUDE.md.
- Drop duplicated portable-mode and frontend-stamp sections; cut adverbs.
- Add a top-of-file directive instructing readers to consult the relevant
  per-directory CLAUDE.md before editing that layer.
- Move "For Developers" setup steps from README to docs/CONTRIBUTOR_GUIDE.md
  and replace the README block with a pointer.
- Add a Screenshots section to README with all 8 images in
  assets/screenshots/ laid out as a two-column gallery.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Communication style section near the top: plain words, one concept
  per message, prompt at decision points. Sets the rule that the new
  slash commands enforce via CHECKPOINTs.
- Code deduplication (DRY) section under cross-cutting design decisions:
  2/3+ extraction threshold, magic-literal calibration, anchor examples
  already in-tree, the documented tolerated exception
  (CATEGORY_SUBTREES <-> DATAFORGE_KEEP_SUBPATHS), and an anti-premature-
  abstraction warning.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ement

Six project-level slash commands under .claude/commands/ that enforce the
documented standards via human-in-the-loop checkpoints. .gitignore now
permits the commands/ directory while keeping settings.local.json local.

Workflow commands:
- /start_release major|minor|patch: open the next release/X.Y.Z off main,
  bump VERSION.TXT, and commit the kickoff. Checkpoint before the
  destructive branch-create.
- /begin_work <issue> <target>: load issue context, resolve the release
  branch (reuse unmerged, otherwise /start_release), create an
  issue/<NN>-<slug> feature branch, then plan-in-chunks and implement
  step-by-step with a CHECKPOINT after each chunk.
- /pull_request: open the branch as a DRAFT PR, walk the self-review
  (test coverage -> docs sync -> standards) one section at a time, then
  offer to mark ready. Body includes Testing Checklist, Testing performed
  block (--testing flag), Post-merge QA, and an attribution footer.

Quality checks (each Critical/Major/Minor with verdict line and
end-of-run checkpoint):
- /standards_check: portable mode, threading, COL_*, DataForge coverage,
  worker settings access, Frontend stamp, DRY duplication.
- /docs_sync_check: tutorial widget validity, HELP/ABOUT string drift,
  workflow currency, feature parity vs README.
- /test_coverage_check: non-exempt code without tests (Critical), stale
  test branches (Major), exempt code flagged for manual smoke (Minor).

Contributor guide gets:
- PR scope and size section (400-line / 8-file / mixed-concern signals).
- AI Usage TLDR drawing on Anthropic's Claude Code best practices.
- Slash-commands listing describing each command's new
  checkpointed/severity-grouped behavior.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant