@lifeaitools/rdc-skills 0.36.1 → 0.37.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,34 +0,0 @@
1
- ---
2
- id: 2026-09-17-release-mcp-registry-split
3
- date: "2026-09-17"
4
- skill: release
5
- session: 01a07b0d-e74e-7601-af20-9caae7e94b71
6
- scope: architectural
7
- status: open
8
- area: infra
9
- links:
10
- commits: [d39104709bf0035f84a8001cc6c30e5c5e0d9c13]
11
- memory: []
12
- work_items: [5f7618b4-cf32-4460-8a3a-761f0161b847]
13
- ---
14
-
15
- ## What happened
16
-
17
- rdc-skillsv0.36.0 tag triggered npm workflow35178348993: packing succeeded,
18
- registryPUT returned404, and npm version lookup remained404. Independently,
19
- the existing public MCP tag updater served0.36.0 at the exacttagSHA with45skills;
20
- connected convo retrieval and remote tests passed. Prior0.35.26 workflow also
21
- shows a PUT404 although that version is now in npm.
22
-
23
- ## Root cause
24
-
25
- Two release consumers advance independently: the MCP host follows mergedtags,
26
- while npm requires a successful authenticatedpublish. A live MCP cannot prove
27
- npm distribution, nor does failednpm publication prove the MCP is stale. The
28
- underlying registry permission/trustedpublisher cause is not established by404.
29
-
30
- ## The fix / rule
31
-
32
- Keep runtimeSHA/catalog and npmversion/provenance as distinct release evidence.
33
- Preserve the failedjob; inspect publisherconfiguration with the packageowner
34
- before changing permissions or retrying. No authboundary repair shipped here.