Back to Signal Feed
CodeTracked since May 19, 2026

Fix slack-channel MCP sync so upstream tests are mirrored and CI no longer fails with no-tests-found

Updated the slack-channel vendoring rules in `sources.yaml` by removing `*.test.ts` and `*.spec.ts` from the exclude list and adding `features/**` to include, preventing test files from being dropped while `bun test` remains in the mirrored `package.json`.

jeremylongshore/claude-code-plugins-plus-skillssources.yamlslack-channelbun test

What Happened

  • Updated the slack-channel vendoring rules in `sources.yaml` by removing `*.test.ts` and `*.spec.ts` from the exclude list and adding `features/**` to include, preventing test files from being dropped while `bun test` remains in the mirrored `package.json`.
  • Updated the slack-channel vendoring rules in `sources.yaml` by removing `*.test.ts` and `*.spec.ts` from the exclude list and adding `features/**` to include, preventing test files from being dropped while `bun test` remains in the mirrored `package.json`.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Corrected a deterministic configuration bug in the external-sync mirror process that excluded upstream test files while still keeping the upstream test command, causing the job to exit with "No tests found" even though the upstream repo had tests.

Why Track This

Why It Matters

Slack-channel MCP plugin maintainers and CI operators will now get real test pass/fail feedback from this plugin instead of a misleading pre-test failure, reducing blind spots in CI and making regressions in plugin behavior visible earlier. The fix also restores test coverage for mirrored policy/journal/supervisor paths by including `features/**` and removing test-file exclusions from sync, so the mirrored plugin’s `bun test` command can actually execute its suites. Continue monitoring whether other MCP plugin runs still short-circuit on first failures and whether failures are still labeled as noisy, because hidden failures would keep additional coverage gaps unseen.

Impact

Slack-channel MCP plugin maintainers and CI operators will now get real test pass/fail feedback from this plugin instead of a misleading pre-test failure, reducing blind spots in CI and making regressions in plugin behavior visible earlier. The fix also restores test coverage for mirrored policy/journal/supervisor paths by including `features/**` and removing test-file exclusions from sync, so the mirrored plugin’s `bun test` command can actually execute its suites. Continue monitoring whether other MCP plugin runs still short-circuit on first failures and whether failures are still labeled as noisy, because hidden failures would keep additional coverage gaps unseen.

What To Watch Next

  • Watch whether jeremylongshore/claude-code-plugins-plus-skills becomes a repeated pattern.
  • Track follow-up changes around Model Context Protocol.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: other_mcp_plugins_may_still_short_circuit_ci, no_tests_found_vs_tests_failed_misclassification.
Open Topic TimelineOpen Technical EventOpen Original Sourceother_mcp_plugins_may_still_short_circuit_ci / no_tests_found_vs_tests_failed_misclassification / sync_glob_patterns_changes_can_reintroduce_missing_tests

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

jeremylongshore/claude-code-plugins-plus-skills PR #745: fix(sync): stop stripping upstream tests from slack-channel mirror (claude-7tig.1)

A deterministic sync-config mismatch was fixed by re-aligning include/exclude patterns, so upstream slack-channel tests are now copied into the mirror and the `test (mcp-plugins)` CI step stops failing before tests run.