[tnunamak]

Summary

• republish icloud-notes-playwright@0.2.0 so the committed artifact matches the current manifest ordering on main
• update artifactSha256 in connector-index.json to match the republished tarball

Why

context-gateway currently cannot resolve the latest data-connectors/main because connector-index.json expects the current icloud-notes manifest ordering, but the committed tarball at artifacts/icloud-notes-playwright/icloud-notes-playwright-0.2.0.tgz still contains the older manifest bytes. This makes the branch publication-inconsistent.

Validation

• CONNECTOR_ARTIFACT_REF=main node scripts/generate-connector-index.mjs
• node scripts/generate-connector-index.mjs --check
• verified packaged ./manifest.json sha256 is 550ba20690d3d16d809686df73f9f23f18005dd5763ce6b631a17d4d7da370c4

[github-actions]

Schema Health Check — 6 issue(s) found

41/47 scopes consistent | 0 missing schema files | 6 not in Gateway | 0 metadata drift | 0 orphaned

View issues

Not registered in Gateway:

Scope	Connector	Added in PR?
instagram.following	instagram-playwright
steam.profile	steam-playwright
steam.games	steam-playwright
steam.friends	steam-playwright
icloud_notes.notes	icloud-notes-playwright
icloud_notes.folders	icloud-notes-playwright

These issues should be resolved before connectors can be used by Personal Servers.