docs: prepare ByteFolk organization handle migration

[PeterGuy326]

Tracking record

Refs #20

Consumed revision: R1, the initial ready issue body last updated at 2026-09-01T03:36:09Z.

Base: 8ba2324e43dcc34bf811f8ac9b68f85750571fc4
Candidate head: 1f1d9fcc667ad35f7983b930cda52b0584006795

Summary

• Move the organization profile, repository links, release/CI badges, security routes, issue contacts, and governance handle references to bytefolk.
• Preserve the published npm scope @fullstack-ai-infra/* and the legal copyright identity.
• Keep layout, product claims, policy behavior, and CI behavior unchanged.

This is a cutover-preparation slice. It does not rename the organization and must not merge before the coordinated cutover.

Acceptance criteria

Acceptance criterion	Status	Implementation / evidence
Isolated owner-coordinate PR from current main	PASS	Dedicated branch at the base/head SHAs above
Public profile and organization entry points use bytefolk	PASS	Profile, badges, security routes, issue contacts, and policy references updated
Old GitHub owner coordinate is absent	PASS	Negative scan reports old_github_owner_coordinates=0
npm @fullstack-ai-infra/* remains unchanged	PASS	npm badge and package URL retained
Legal identity remains unchanged	PASS	LICENSE has no diff
Live links resolve	NOT VERIFIED	Requires the organization rename
Required CI passes without bypass	PASS	Governance succeeded on exact head (run)

Validation ledger

Command or check	Expected	Actual
ruby scripts/validate-governance.rb	Governance/profile files validate	PASS: 5 forms, config, 7 required files, and local links validated
git diff --check	No whitespace errors	PASS
Old GitHub-owner coordinate scan	Zero old GitHub/raw/API/badge coordinates	PASS: 0
git diff --exit-code origin/main -- LICENSE	Legal text unchanged	PASS
npm-scope readback	npm badge retains @fullstack-ai-infra/digital-employee	PASS
GitHub Actions: Governance	Required workflow passes	PASS (run)

Tests and coverage

• Tests added or changed: none; this is a documentation/repository-coordinate migration.
• Coverage: unchanged.
• Intentionally uncovered: external bytefolk links before cutover.
• Changelog: this repository has no changelog; the profile and policies are the user-visible record.

Change classification

• User-visible behavior
• Internal refactor or maintenance
• Documentation only
• Build, CI, dependency, or repository configuration
• Breaking change
• Security-sensitive change

Risk and rollback

• Risk: merging before the rename would publish not-yet-live links.
• Rollback: close this PR before cutover, or use a normal revert PR after merge.
• Compatibility: npm identity and legal text are unchanged.

Breaking or security notes

None. Security-reporting coordinates move; reporting policy and access controls do not.

Author checklist

• Linked issue is ready and the branch starts from current main.
• Applicable validation, diff, invariant, and sensitive-pattern checks passed.
• No unrelated files, generated artifacts, dependencies, or secrets are included.
• Regression tests are not applicable to a coordinate-only documentation change.
• Results and the pre-cutover limitation are reproducible.
• Required CI is green and the PR is ready for independent review.

Automated assistance prepared the mechanical diff and evidence; the human submitter remains accountable.

Reviewer notes

Please focus on the npm/legal allowlist and the security-reporting/profile link destinations.

[Bindy-lbb]

Independent review (Bindy-lbb). Prose-only migration of GitHub URLs (issue templates, security/support links, profile README, org docs) to the bytefolk handle. Verified all references are plain GitHub coordinates, not npm scope or schema identifiers. CI (Governance) green. No P0/P1. Approving.