a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
37 lines
1.6 KiB
YAML
37 lines
1.6 KiB
YAML
# CodeRabbit configuration — golem15com/msd-core
|
|
#
|
|
# Schema: https://docs.coderabbit.ai/reference/yaml-template/
|
|
#
|
|
# Project context: MSD ships a CLI tool + an agent runtime, not a documented
|
|
# public library. We carry rich JSDoc on internal helpers that warrant it
|
|
# (see bin/install.js, msd-core/bin/lib/*.cjs) but we do not enforce a
|
|
# blanket docstring coverage bar — see issue #2932 for rationale.
|
|
|
|
reviews:
|
|
pre_merge_checks:
|
|
# Disable docstring coverage check.
|
|
#
|
|
# The check produces false-positive warnings on PRs whose new code is
|
|
# entirely test files: it counts test(...) / beforeEach / afterEach
|
|
# arrow-function callbacks as functions and then reports 0% coverage
|
|
# because nothing has JSDoc. There is no per-check path filter in CR's
|
|
# documented schema that would let us exclude tests/** while keeping
|
|
# the check active elsewhere, and the top-level path_filters approach
|
|
# would silence ALL CR review on tests (security scans, out-of-scope
|
|
# checks, line-level findings) which we want to keep.
|
|
#
|
|
# All other CR pre-merge checks (out-of-scope, security, title) remain
|
|
# at their defaults.
|
|
docstrings:
|
|
mode: off
|
|
|
|
tools:
|
|
# Disable ESLint. The repo intentionally does not use ESLint — it ships
|
|
# its own targeted lint scripts (scripts/lint-no-source-grep.cjs, plus
|
|
# the `lint:tests` npm script) that enforce repo-specific test-quality
|
|
# invariants. Adding ESLint config purely to satisfy CR would add an
|
|
# external dependency (CONTRIBUTING.md: "No external dependencies in
|
|
# core") and overlap with the existing custom lint surface.
|
|
eslint:
|
|
enabled: false
|