You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to the B4.run rename merged in #595 and version update #596.
Release coordination:#597 is owned by the active release maintainer. Do not interrupt its CI, mutate the active candidate, or remove credentials it needs. Execute this issue only when its dependencies below are satisfied.
Owner: Product/marketing owner with account administrators. Dependencies: Read-only inventory can begin now; publication messaging depends on #598; old-domain decisions depend on confirmed redirect policy.
Problem: Repository assets and the live website were updated, but off-repository channels and account ownership have not been comprehensively established.
Files/surfaces:apps/web/app, apps/web/content, apps/web/public, README.md, SECURITY.md, and the accounts actually identified by owners. Add an inventory under docs/superpowers/ without credentials.
Create a table of account/resource, URL/ID, owner, old public name/domain, current usage evidence, required action, and verification result. Ask owners about social profiles, design libraries, community/chat, newsletters/email templates, support/contact addresses, analytics, search consoles, and vendor billing/support display names. Record “not used” only when verified; otherwise record “unknown.”
Inspect public profile links, social preview cards, favicons, downloadable brand assets, demo descriptions/transcripts, and marketing emails for old identity. Separate historical articles from active product claims.
In identified search/analytics accounts, verify ownership of b4.run, sitemap ingestion, canonical/OG URLs, and event continuity as applicable. Inspect crawl/index coverage after the account's normal processing period. Do not add a new analytics vendor simply to complete this checklist.
Verify designated B4 contact/support mailboxes receive mail before replacing public contact addresses; configure only the DNS records required by the chosen existing mail provider.
Prepare concrete profile/email/design edits for their owners. Obtain explicit authorization before publishing announcements or sending messages; this planning task does not authorize outreach.
Acceptance: Every identified channel has a named owner and disposition; current public assets point to B4.run and working contact paths; unresolved access/ownership is tracked explicitly, not silently marked complete.
Confirmed redirect policy — 2026-09-10 UTC: The owner explicitly chose to leave the existing redirects in place. Preserve the old-domain redirects to b4.run and GitHub repository rename redirects. This supersedes the initial no-redirect request. Runtime/package compatibility aliases remain prohibited. Record this resolved decision in the current cutover documentation under #600.
Execution update — 2026-09-09
Updated the Cacheplane organization profile README, which still advertised the old framework: product B4.run, @b4run/sdk, b4 build, final repository URL, and b4.run/docs. Verified the committed content through the API. Commit: cacheplane/.github@8040b3c . No B4 workflow was changed. Broader account-owner inventory and other marketing surfaces remain open.
Follow-up execution — 2026-09-09
The committed inventory is in PR #618 at docs/superpowers/runbooks/2026-09-09-b4-marketing-inventory.md. All 83 sitemap pages returned 200 with no obsolete Blob references; current metadata, brand assets and demo URLs were verified. The /brand route was intentionally removed in #137, but stale links remained. PR #618 repairs those links to the existing brand ZIP and synchronizes manifest homepages. The authenticated Vercel preview renders the corrected download link; production verification awaits integration. Resend lists only verified domains belonging to Cacheplane and Threadplane, with no B4 sender domain. Social/design/analytics/search/email account ownership remains explicitly unknown; no announcements or mail were sent.
Additional external profile — 2026-09-09
Found the live OpenSSF Best Practices profile 13317, owned by Brian Love (account ID 53316). The public profile still identifies the project as dawnai with the old homepage and repository. Authenticated edit access is available.
Prepared exactly ten field changes in its edit form: name B4.run, homepage https://b4.run, repository https://github.com/cacheplane/b4run, and replacement of the old repository prefix in seven existing contribution/license/reporting evidence links. No certification answers were edited. The pre-edit public snapshot contains 196 status fields and a passing badge at 100%.
Submitted and verified — 2026-09-10 UTC: the owner approved submission after the data-license notice was disclosed. The public OpenSSF JSON now reports B4.run, https://b4.run, and https://github.com/cacheplane/b4run. All seven evidence links were updated by exact repository-prefix replacement. Comparison with the pre-edit snapshot found exactly the ten intended branding fields plus the server-managed updated_at and repo_url_updated_at timestamps changed. All 194 status-related fields and all other claims remain unchanged; the passing badge remains at 100%. No automatic answer completion was run. This external profile correction is complete; the broader account-owner/search/email inventory remains open.
Production brand repair completed — 2026-09-10 UTC
PR #618 merged as 777138ccf7b9599f1e7041c9d07d01a8c72d3781. Live homepage and 404-page links now download the existing brand ZIP; the merged issue-template link matches. Public manifest homepage is /, and the live ZIP exactly matches the committed archive (SHA256 5026d1dbb08e85af2710d5ff4b1c326ab1339914c64c9301ed077971dd763571); its embedded manifest is synchronized and all 22 entries pass CRC. The intentional /brand route removal remains. Existing old-domain redirects remain in place under the owner's explicit decision.
The deployment-pending observations in the initial inventory are now superseded by this verification. OpenSSF is also complete. Keep this issue open for the explicitly unknown social, design, search/analytics and email account ownership; do not add vendors or publishing complexity to fill inventory rows.
Owner deferral — 2026-09-10 UTC
The owner has explicitly deferred the remaining external-account inventory. Keep this issue open for later; no account discovery, outreach, or additional vendor setup is scheduled in the current pass.
Follow-up to the B4.run rename merged in #595 and version update #596.
Release coordination: #597 is owned by the active release maintainer. Do not interrupt its CI, mutate the active candidate, or remove credentials it needs. Execute this issue only when its dependencies below are satisfied.
Owner: Product/marketing owner with account administrators. Dependencies: Read-only inventory can begin now; publication messaging depends on #598; old-domain decisions depend on confirmed redirect policy.
Problem: Repository assets and the live website were updated, but off-repository channels and account ownership have not been comprehensively established.
Files/surfaces:
apps/web/app,apps/web/content,apps/web/public,README.md,SECURITY.md, and the accounts actually identified by owners. Add an inventory underdocs/superpowers/without credentials.b4.run, sitemap ingestion, canonical/OG URLs, and event continuity as applicable. Inspect crawl/index coverage after the account's normal processing period. Do not add a new analytics vendor simply to complete this checklist.Acceptance: Every identified channel has a named owner and disposition; current public assets point to B4.run and working contact paths; unresolved access/ownership is tracked explicitly, not silently marked complete.
Confirmed redirect policy — 2026-09-10 UTC: The owner explicitly chose to leave the existing redirects in place. Preserve the old-domain redirects to
b4.runand GitHub repository rename redirects. This supersedes the initial no-redirect request. Runtime/package compatibility aliases remain prohibited. Record this resolved decision in the current cutover documentation under #600.Execution update — 2026-09-09
Updated the Cacheplane organization profile README, which still advertised the old framework: product B4.run, @b4run/sdk, b4 build, final repository URL, and b4.run/docs. Verified the committed content through the API. Commit: cacheplane/.github@8040b3c . No B4 workflow was changed. Broader account-owner inventory and other marketing surfaces remain open.
Follow-up execution — 2026-09-09
The committed inventory is in PR #618 at docs/superpowers/runbooks/2026-09-09-b4-marketing-inventory.md. All 83 sitemap pages returned 200 with no obsolete Blob references; current metadata, brand assets and demo URLs were verified. The /brand route was intentionally removed in #137, but stale links remained. PR #618 repairs those links to the existing brand ZIP and synchronizes manifest homepages. The authenticated Vercel preview renders the corrected download link; production verification awaits integration. Resend lists only verified domains belonging to Cacheplane and Threadplane, with no B4 sender domain. Social/design/analytics/search/email account ownership remains explicitly unknown; no announcements or mail were sent.
Additional external profile — 2026-09-09
Found the live OpenSSF Best Practices profile 13317, owned by Brian Love (account ID 53316). The public profile still identifies the project as
dawnaiwith the old homepage and repository. Authenticated edit access is available.Prepared exactly ten field changes in its edit form: name
B4.run, homepagehttps://b4.run, repositoryhttps://github.com/cacheplane/b4run, and replacement of the old repository prefix in seven existing contribution/license/reporting evidence links. No certification answers were edited. The pre-edit public snapshot contains 196 status fields and a passing badge at 100%.Submitted and verified — 2026-09-10 UTC: the owner approved submission after the data-license notice was disclosed. The public OpenSSF JSON now reports
B4.run,https://b4.run, andhttps://github.com/cacheplane/b4run. All seven evidence links were updated by exact repository-prefix replacement. Comparison with the pre-edit snapshot found exactly the ten intended branding fields plus the server-managedupdated_atandrepo_url_updated_attimestamps changed. All 194 status-related fields and all other claims remain unchanged; the passing badge remains at 100%. No automatic answer completion was run. This external profile correction is complete; the broader account-owner/search/email inventory remains open.Production brand repair completed — 2026-09-10 UTC
PR #618 merged as
777138ccf7b9599f1e7041c9d07d01a8c72d3781. Live homepage and 404-page links now download the existing brand ZIP; the merged issue-template link matches. Public manifest homepage is/, and the live ZIP exactly matches the committed archive (SHA2565026d1dbb08e85af2710d5ff4b1c326ab1339914c64c9301ed077971dd763571); its embedded manifest is synchronized and all 22 entries pass CRC. The intentional/brandroute removal remains. Existing old-domain redirects remain in place under the owner's explicit decision.The deployment-pending observations in the initial inventory are now superseded by this verification. OpenSSF is also complete. Keep this issue open for the explicitly unknown social, design, search/analytics and email account ownership; do not add vendors or publishing complexity to fill inventory rows.
Owner deferral — 2026-09-10 UTC
The owner has explicitly deferred the remaining external-account inventory. Keep this issue open for later; no account discovery, outreach, or additional vendor setup is scheduled in the current pass.