Document importer SDK lineage and npm visibility blocker

Merged
UN
3mo ago
+41-2

Summary

  • track GitHub issue #749 as a duplicate-safe SDK-first child with rich importer/exporter runtime lineage
  • record the exact merged-main v2026.7.26 access-first recovery result and npm E403 authorization blocker
  • leave both worked PM items open and unclaimed, with zero in-progress items

PM items

Verification

  • pnpm build
  • pnpm changelog:pm:check with pm-changelog 2026.7.26, unchanged
  • pm health --check-only --summary --json (ok: true, zero warnings)
  • pm validate --check-resolution --check-history-drift --json (history drift zero; existing resolution metadata warning remains)
  • pm list-in-progress --limit 50 (zero)
  • git diff --check

External release state

The workflow is fail-closed and does not republish the immutable version. npm package visibility remains private because the release environment token receives E403 on the access mutation; issue #746 contains the maintainer credential action.

Summary by Sourcery

Record PM history and reminder updates for npm auto-release visibility and add tracking artifacts for the SDK importer runtime item.

Chores:

  • Update pm-7zs0 history and reminder entries to reflect npm auto-release visibility and authorization outcome.
  • Add pm-i7indd issue and history files to track the SDK importer/runtime lineage work without marking it in-progress.

Summary by cubic

Adds PM tracking for the importer/exporter SDK runtime lineage and records the v2026.7.26 npm visibility failure. Creates issue pm-i7indd (linked to GitHub #749) for injecting a host‑bound SDK into ImportExportContext, and updates the release reminder/history to note that npm access set status=public @unbraind/pm-cli returned E403; workflow remains fail‑closed and both items stay open/unclaimed.