[Migration] Move npm packages from @fullstack-ai-infra to @bytefolk

[PeterGuy326]

Status

APPROVED / BLOCKED — target and exact migration plan are approved; npm authentication and @bytefolk ownership readback are still required before registry writes.

Product decision recorded on 2026-09-02: migrate every active @fullstack-ai-infra/* identity and consumer to the corresponding @bytefolk/* identity. Preserve the existing public/private/fixture intent. Independent @context/*, @org-workbench/*, and unscoped private packages are outside this scope.

This issue is the organization-level execution ledger. It does not authorize exposing credentials, unpublishing packages, deleting the old npm organization, or bypassing release gates.

Verified baseline

• Local registry access works, but the configured npm credential returns E401.
• Therefore @bytefolk npm organization ownership, operator role, 2FA policy, team access, and Trusted Publisher capability are not yet proven.
• Public old packages:
  • @fullstack-ai-infra/digital-employee@0.6.0
  • @fullstack-ai-infra/digital-employee-core@0.6.0
  • @fullstack-ai-infra/mem-mcp@0.1.1
• All target @bytefolk/* packages currently return anonymous 404. This is not ownership proof.
• @fullstack-ai-infra/ui, engine, and doc-collaboration also return 404 and must not be described as already published.
• The three old public packages are not deprecated. They remain the rollback path; none will be unpublished.

Approved identity map

Current identity	Target identity/version	Classification	Registry action
@fullstack-ai-infra/digital-employee@0.6.1 source; old public latest 0.6.0	@bytefolk/digital-employee@0.6.1	public replacement	publish
@fullstack-ai-infra/digital-employee-core@0.6.1 source; old public latest 0.6.0	@bytefolk/digital-employee-core@0.6.1	public replacement	publish
@fullstack-ai-infra/digital-employee-engine@0.4.0	@bytefolk/digital-employee-engine@0.4.0	dormant/internal	rename source, set private, do not publish
@fullstack-ai-infra/ui@0.2.0	@bytefolk/ui@0.2.1	unpublished public-intent	first public release
@fullstack-ai-infra/ui-pack-consumer-fixture@0.0.0	@bytefolk/ui-pack-consumer-fixture@0.0.0	private fixture	rename source, do not publish
@fullstack-ai-infra/doc@0.1.0	@bytefolk/doc@0.1.0	private workspace	rename source, do not publish
@fullstack-ai-infra/doc-cli@0.1.0	@bytefolk/doc-cli@0.1.0	private workspace	rename source, do not publish
@fullstack-ai-infra/doc-collaboration@1.0.0	@bytefolk/doc-collaboration@1.0.0	internal service	rename source, set private, do not publish
@fullstack-ai-infra/digital-employee-platform@0.1.0	@bytefolk/digital-employee-platform@0.1.0	private workspace	rename source, do not publish
@fullstack-ai-infra/ui consumer coordinates	@bytefolk/ui@0.2.1	Doc / Org Workbench consumers	switch only after verified release

The UI version is 0.2.1 because immutable Git tag v0.2.0 already exists and predates this package identity.

Implementation records

Repository/surface	Source of truth
Digital Employee packages and release	bytefolk/digital-employee#247
Design System public package	bytefolk/design-system#19
mem-mcp package, binary release, MCP/cache identities	bytefolk/mem#153
Doc private workspaces and vendored UI tarball	bytefolk/doc#36
Quickstart public consumer	bytefolk/digital-employee-quickstart#20
Org Workbench UI consumer	bytefolk/roleweave#121
Private marketplace platform	https://github.com/bytefolk/digital-employee-platform/issues/10
Organization/profile npm surface	#25

Exact registry write set and operator boundary

Responsible human operator: npm organization owner PeterGuy326, after interactive npm login and private ownership/role verification.

No write below runs until npm whoami, org membership/role, team/access, 2FA, and package-name control pass from the authorized machine.

1. Bootstrap new package identities with interactive 2FA, public access, and next only:
   • @bytefolk/digital-employee-core@0.6.1-rc.0
   • @bytefolk/digital-employee@0.6.1-rc.0
   • @bytefolk/ui@0.2.1-rc.0
   • @bytefolk/mem-mcp@0.1.2-rc.0
2. Bind one Trusted Publisher per package:
   • Digital Employee packages: bytefolk/digital-employee, workflow release.yml, environment npm-release
   • UI: bytefolk/design-system, workflow npm-publish.yml, environment npm-release
   • mem-mcp: bytefolk/mem, workflow npm-publish.yml, environment npm-release
3. Publish the four stable versions to next through GitHub OIDC using GitHub-hosted Node 24, npm >=11.15.0, id-token: write, and no long-lived npm token.
4. Verify clean install/import/CLI behavior, release assets, metadata, access, provenance, signatures, and Trusted Publisher readback.
5. Promote only verified stable versions to latest with interactive 2FA.
6. Grant reviewed bytefolk:developers package access, then require 2FA and disallow tokens only after OIDC is proven.
7. Migrate executable consumers, docs, lockfiles, vendored artifacts, badges, MCP identity, and cache compatibility.
8. Only after consumer proof, deprecate all versions of the three old public packages with an explicit replacement message.
9. Never unpublish, overwrite, reuse a published name+version, move an immutable Git tag, or delete the old npm organization during rollout.

Ordered rollout and rollback

Order: source/release PRs → RC bootstrap to next → Trusted Publisher → stable OIDC publish to next → readback/smoke → latest → consumer PRs → old-scope deprecation.

Rollback:

• Before consumer cutover, leave old packages untouched and stop the rollout.
• After cutover, restore consumers to the still-installable old coordinates if necessary.
• Point latest back to the last verified new-scope version and publish a higher patch; never overwrite/unpublish.
• Clear old-package deprecation if rollback requires it.
• Revoke and recreate an incorrect Trusted Publisher binding rather than introducing a long-lived automation token.

Acceptance criteria

• Owner control of bytefolk on npm and responsible operator permissions are privately verified; only the sanitized verdict is recorded here.
• Registry inventory distinguishes published, unpublished, private, internal, and fixture identities.
• Per-package target names, versions, exclusions, and nonpublish protections are approved.
• Bootstrap, OIDC, provenance, consumer migration, deprecation, and rollback plans are reviewed and exact.
• Separate repository implementation records exist.
• Four new public packages pass registry and clean-environment proof.
• All active consumers and package surfaces use ByteFolk.
• Old public packages are deprecated only after replacement proof; none are unpublished.

Current blocker

The authorized operator must renew npm authentication on this machine without sharing credentials or one-time codes. Until then, code preparation and review may proceed, but no npm organization/package/access/dist-tag/deprecation/Trusted Publisher write is possible.

[PeterGuy326]

Public registry readback; HOLD remains (2026-09-01T16:56Z)

No npm login or registry write was performed.

Anonymous public readback currently proves only:

• @fullstack-ai-infra/digital-employee: latest=0.6.0
• @fullstack-ai-infra/digital-employee-core: latest=0.6.0
• @fullstack-ai-infra/mem-mcp: latest=0.1.1
• several source identities and sampled @bytefolk/* target names return 404 anonymously.

A 404 does not distinguish unavailable, unpublished, private, retired, or fixture state, and it does not prove control or availability of the @bytefolk scope. GitHub organization ownership is not npm ownership.

The exact owner input is still missing: on an authorized npm account, verify bytefolk organization/scope control, membership, 2FA/provenance policy, Trusted Publisher capability, and the private/public inventory without exposing credentials. Then record per-package classification and target names here. Only after Product Owner review may a separate implementation record enumerate exact publisher, package, version, dist-tag, compatibility, consumer, deprecation, and rollback writes.

Status remains HOLD. This comment authorizes no login, scope reservation, membership, 2FA, token, Trusted Publisher, publish, dist-tag, deprecate, unpublish, or other registry action.

[PeterGuy326]

schemaVersion: requirement-decision.v1
canonicalIssue: "https://github.com/bytefolk/.github/issues/22"
previousRevision: R1
resultingRevision: R2
resultingStatus: blocked-owner-verification
decisionType: target-scope-approved
oldDecision: "Possible migration from @fullstack-ai-infra to @bytefolk remained undecided."
newDecision: "Migrate every active source identity currently under @fullstack-ai-infra, and every active consumer of those identities, to the corresponding @bytefolk package name. Preserve public/private/fixture classification; do not publish private packages or fixtures. Existing independent @context/* and @org-workbench/* scopes remain outside this decision."
approver: "@PeterGuy326"
decidedAt: "2026-09-01T17:07:00Z"

Owner decision

The target namespace is approved: all @fullstack-ai-infra/* package identities move to their corresponding @bytefolk/* identities.

The rollout order is fixed:

1. verify that the authenticated npm operator controls the bytefolk organization/scope;
2. freeze the exact package map, classification, versions, publish access, Trusted Publisher bindings, consumers, and rollback;
3. publish and publicly read back every approved replacement package;
4. migrate source and consumers with clean lockfiles and compatibility evidence;
5. deprecate, but do not unpublish, old public packages only after replacement/consumer proof.

Private packages remain private-only. Fixtures remain non-publication candidates. Historical registry artifacts and Releases remain immutable.

Current blocker

The local npm credential currently returns E401 Unauthorized from npm whoami. Therefore @bytefolk organization control, membership, 2FA policy, package permissions, and Trusted Publisher capability are still NOT VERIFIED. Status remains HOLD/blocked until the owner re-authenticates on the authorized machine.

This decision authorizes migration planning and scoped repository implementation records. It does not yet authorize an npm organization creation, package publication, access change, dist-tag, deprecation, unpublish, token, membership, 2FA, or Trusted Publisher write because the exact package/version/write manifest has not been verified and approved.

[waterbro-8]

公开注册表回读补充(2026-09-03)——不解除 HOLD、不改状态、不指派

给本条的 owner @PeterGuy326 补两条今天量到的事实。两条都来自匿名公开端点,没有做任何 npm 登录、没有写注册表、没有动任何凭据。

@fullstack-ai-infra/mem-mcp
  versions          = ["0.1.1"]          ← 没有 0.1.0
  dist-tags.latest  = "0.1.1"
  0.1.1._npmUser.name = "huyizhou326"    ← 个人 npm 账号,不是 "GitHub Actions"
  0.1.1.dist keys   = fileCount, integrity, shasum, signatures, tarball, unpackedSize
                       ↑ 没有 attestations:这次发布没有 provenance
  0.1.1 time        = 2026-08-31T16:53:10.064Z
  (GitHub Release v0.1.1 = 2026-08-31T06:34:08Z,早约 10 小时 → 发布是手工补的)

@fullstack-ai-infra/digital-employee
  0.6.0._npmUser    = { name: "GitHub Actions", email: "npm-oidc-no-reply@github.com",
                        trustedPublisher: { id: "github",
                            oidcConfigId: "oidc:b5e38816-d6ef-4103-8eae-1ce7e8682a24" } }
  0.6.0.dist.attestations.provenance.predicateType = https://slsa.dev/provenance/v1
  0.6.0 time        = 2026-08-28T17:26:27.245Z
  发布方 job: bytefolk/digital-employee run 33193084146 / job 98928568129(npm-root)

这三条对本条的意义

1. @fullstack-ai-infra 这个 scope 已经足够建 GitHub OIDC Trusted Publisher。 de 的 oidcConfigId 就是证据。所以 bytefolk/mem 那边等的那条 npm 记录,前置条件不是 @bytefolk 归属被证实,而是"当初给 de 建记录的那个账号/那次登录"。本条 HOLD 卡住的迁移(改包名)和 mem 发版要的记录是两件事,可以解耦。
2. mem 在 npm 上的历史发布全部没有 attestation,包括最新的 0.1.1(个人账号手工发)。这条正是"为什么需要 OIDC 路径"的最强论据,值得进本条的证据块。
3. 一条需要立刻确认的风险:de 那条成功记录建于 08-28,当时 GitHub org 还叫 fullstack-ai-infra(该 job 日志里 GH_REPO: fullstack-ai-infra/digital-employee),而 org 在 09-02 已改名 bytefolk(API 现在直接把旧名重定向到新名)。npm 匹配的是 OIDC token 里的 GitHub org 名。我没有 npm 侧读权限,这条完全没验证——请在同一个页面确认 de 的记录是否还指向旧 org 名;如果是,de 的下一次发版会挂,而这跟迁移本身无关。

我明确没做

没登录 npm、没读/写任何 secret 或 token、没建或删除任何 Trusted Publisher 记录、没改本条的 state / labels / assignees、没撤回 HOLD。上面所有数字都是匿名 registry.npmjs.org JSON + 公开 Actions job 日志的回读。

[PeterGuy326]

mem-specific decision reconciled: bytefolk/mem#153 (comment)

The @bytefolk/mem-mcp@0.1.2 route in this ledger is confirmed; the 2026-09-03 keep-old-scope exception for mem is superseded. Source/release preparation is proceeding in mem#153. The 2026-09-10 npm authentication readback is ENEEDAUTH; the existing authentication, ownership, 2FA, Trusted Publisher, release and promotion gates remain unchanged. No other package's scope or publication status is changed by this update.