M3 — Consolidate Scout duplicates
Open
@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 M3 (#37128). Depends on M0.
Description
Retire the duplication confirmed in M0 across docs/testing/, the docs/core/ slice and the two rules directories — folding each retired file's unique content into the survivor first, not a straight delete. Same method Jose used on the _FOCUSED pair.
Acceptance Criteria
- Every duplication candidate from M0 either consolidated or explicitly ruled out with a reason
-
.cursor/rules/*.mdcreviewed for content that restates a doc instead of pointing at it. Both files read so far (test-context.mdc,java-context.mdc) end in an## On-demandlist of@docs/...pointers, which is the right shape — but each also inlines rules that live in those same docs, andjava-context.mdchas already drifted (see #37577). Decide per rule: keep inline because Cursor needs it without a file load, or replace with the pointer. -
docs/testing/API_TESTING.mdandPERFORMANCE_TESTS.mdruled out as consolidation candidates — both read in full, no overlap withREST_API_PATTERNS.mdorINTEGRATION_TESTS.md(see the correction note in #37578) - Unique content folded into the surviving file before any deletion, verified line by line
- No link left pointing at a deleted file (reachability check from M2 stays green)
- Monitoring gate opened for each merged change
Priority
Medium
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.