dotCMS / dotCMS/core

M0 — Scout context audit (testing, core slice, rules, commands)

Open
#37,576 3 comments 0 reactions 1 assignee View on GitHub

@fabrizzio-dotCMS is already working on this.

Since Sep 16, 2026.

dotCMS : Technical Debt Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Sub-issue of #37124. Scout half of the Rock — mirrors Jose's M0 (#37125).

Description

Inventory contradictions, orphaned files, and duplication across Fabrizzio's slice of the AI context: docs/testing/ (5 files), the docs/core/ slice, .cursor/rules/ (7 files, 453 lines) and .claude/commands/ (7 slash commands). This is the finalized fix-list that M1/M2/M3 execute against. Inventory only — no file changes.

Two areas have never been audited by anyone: .cursor/rules/ and .claude/commands/. Their last commits are all incidental (the Vitest migration, the Angular 22 upgrade, skill governance) — no one has cross-checked their content against real source the way M1–M3 did for docs/backend/.

Acceptance Criteria
  • All 5 docs/testing/ files read and cross-checked — BACKEND_UNIT_TESTS.md carries fabricated content, E2E_TESTS.md is clean; see inventory part 2
    • INTEGRATION_TESTS.md excluded from re-audit — fully rewritten by Jose in #37128; its monitoring gate is tracked separately
  • All .cursor/rules/*.mdc read and cross-checked against real source — findings fixed in #37590 and #37629
  • All 7 .claude/commands/*.md read and cross-checked against real source — finding fixed in #37610
  • docs/core/ slice files read and cross-checked
  • Contradictions confirmed with exact file:line citations, not just "seems off" — for everything audited so far; docs/core/ slice still pending
  • Orphaned files confirmed by verifying they're absent from both CLAUDE.md's navigation and docs/README.md — 7 found, see inventory comment
  • Duplication candidates confirmed or ruled out by reading full file content — API_TESTING.md and PERFORMANCE_TESTS.md both read in full and ruled out
  • Findings published as a structured inventory (in comments)
Two ownership questions to close in this milestone
  • The docs/core/ slice doesn't add up. The split gives Jose 4 files (ARCHITECTURE_OVERVIEW.md, SECURITY_PRINCIPLES.md, ROLLBACK_UNSAFE_CATEGORIES.md, CODE_STRUCTURE.md — the last one now folded into ARCHITECTURE_OVERVIEW.md by #37128) and Fabrizzio 5. After Jose's 3 surviving files, 6 remain: CICD_PIPELINE.md, GITHUB_ISSUE_MANAGEMENT.md, GIT_WORKFLOWS.md, PROGRESSIVE_ENHANCEMENT.md, SDK_BREAKING_CHANGE_CATEGORIES.md, SPEC_KIT_QUICK_START.md. One file is unassigned — decide which, or widen the slice to 6.
  • Four directories belong to no one. docs/cli/ (CLI_OVERVIEW.md, CLI_BUILD_SYSTEM.md — 25 KB combined), docs/claude/GPG_COMMIT_SIGNING.md and docs/test-cases/README.md are all orphaned and claimed by neither Falcon nor Scout. Same gap the Rock already hit with docs/integration/ and resolved as joint ownership in #37129 — needs the same kind of decision, not just a doc fix.
Priority

High

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.