Back to DevLog

Retiring kdp-format across five repos and fixing the leak check

2 min read

I removed kdp-format from all five repositories. The skill content had already been backed up to Quire at commit 6f00e83 in docs/kdp-reference/.

The one real breakage

scan_local_number_leaks built its regexes from the local skill counts. Once kdp-format was gone, local equaled public, so the script started hunting for the correct public strings. It found 10 false positives across README.md, plugin.json, and marketplace.json.

I rewrote the check to gate each number independently against its public counterpart. It stays dormant while local and public counts agree, and re-arms per-number if either diverges. No flag to flip back later.

Reindex caught a pre-existing bug

The skill index claimed 130 total but was wrong in both directions. It counted kdp-format and omitted the goal skill. After reindexing: 130 with goal present and kdp-format gone.

One commit per repo

  • a169469 memstack: local count now equals public count
  • eca8d0d loader: disarm the local-number leak check
  • b9af363 memstack-pro: remove the tracked copy (3 files, 1,543 lines)
  • e016dea adminstack: remove the rules copy (333 lines)
  • d221f25 memstack-pro-site: remove the rules copy (333 lines)

All five repos deployed and verified clean. adminstack uses main as its production branch. The other four use master.

The script does not refresh a running server

scripts/index_skills.py rebuilds the on-disk index but does not refresh a running MCP server's in-memory copy. After running the script, find_skill still returned kdp-format and still omitted goal. The reindex_skills MCP tool fixed both. The dashboard was unaffected because it opens the pickle fresh per request.

Share this post