Repository navigation
Description
Current execution state
All 65 in-scope repository transfers and the private SFL App transfer are complete. The original 67 repository IDs reconcile to 65 hemsoft-dev destinations and two retained private personal hosting repositories, HemSoft/now-leadership-group and HemSoft/set-it-free-loop-site. Thirteen transferred repositories retain their archived state. The name collision preserves both repositories, with the private repository named hs-cli-confluence-search-fhemmer.
The repository transfer receipt and App transfer receipt record the owner-directed repository-first execution. The App now belongs to hemsoft-dev; installation 169090497 covers all current and future organization repositories. No key export, rotation or organization secret delivery is claimed.
Remaining acceptance
- Review and merge the executed report, PR #156. Merged October 8 at 12:36 EDT as
4447b3eff8a797ba77a9a9f16120829b9af424e6. Its separate validator verifies all 65 transfer identities, ref sets, visibility, default branches and archive states from primary API responses. - Obtain explicit owner acceptance of the documented historical fhemmer source-protection evidence limitation. The last owner-browser empty-policy capture preceded transfer by several hours, and the cutover ruleset API returned HTTP 403. The later audit cannot establish a fresh pre-transfer capture. Repository identity and refs are verified; policy preservation is not fully verified. The owner instruction to defer SFL did not waive this separate requirement.
SFL rollout issue #139 remains open for the 52-active-repository rollout and installed runtime proof. The signed rc21 release and both installed pilot qualifications are recorded in PR #156. The executed report has merged. This issue remains open only for explicit owner acceptance of the historical protection-evidence limitation.
Historical preparation gates and provider ledger
The following is the original preparation record. It retains prior decisions and outstanding-at-the-time checkboxes without relabeling them as fresh pre-transfer proof. The current execution state and remaining acceptance above govern this issue.
SFL App ownership and installation completed
The private App is now owned by hemsoft-dev, installed for all current and future organization repositories as installation 169090497. App/client identity, existing private key and permission ceiling are preserved. The existing-key GET-only check passed, and the transfer receipt records the result. No key export, rotation or organization secret write occurred. Canonical immutable rc16 and fresh private download proof completed #136. Reviewer fleet rollout remains in #139; migration evidence reconciliation remains open here.
Owner-directed delivery order: repositories first, SFL afterward. All 65 repository transfers are complete; two private hosting repositories remain in HemSoft. SFL App transfer and credential/reviewer work remain deferred. See #138 (comment) for the final census and preservation results.
Description
Execute the inventory from organization setup after tooling and review authorization are ready for cutover. The baseline is 67 repositories, including archived/private repositories and the duplicate hs-cli-confluence-search name.
sfl-app is currently owned by the HemSoft User, App ID 4448946. Its registration and installations need separate migration checks. Native Codex is an OpenAI-owned App and must be installed/connected for the new organization, not transferred to it.
Why
The new organization must become the actual owner while repositories retain their data, access, integrations, and working automation.
Goal
Move the 65 in-scope repositories and the owned SFL App, then restore integrations against canonical destination URLs. Retain HemSoft/now-leadership-group and HemSoft/set-it-free-loop-site in the personal account per Franz's October 6 decision; preserve their visibility, archive state and hosting.
Mandatory pre-transfer gates
Franz explicitly moved the following owner-verification work from #135 here on October 6, 2026. Complete every applicable gate for the 65 transfer targets before transferring any repository or App, including a pilot. Also verify any shared App-transfer impact on the two retained personal repositories. A missing, inaccessible, or uncertain entry blocks cutover.
- Refresh the 67-repository migration baseline, all App repository selections, protections, runner registrations and groups, and environment secret/variable name inventories. Reconfirm fhemmer protection settings through owner access when its API is inaccessible. The current supplemental evidence observes no fhemmer rulesets, one repository runner under HemSoft/yahtzee, and empty credential-name lists in all 16 environments; refresh rather than assume those facts remain current.
- Complete an owner-verified external integration ledger for every transfer target and any retained repository affected by App transfer: provider/resource owner, exact resource URL, billing/plan dependency, credential source and validity, affected workflow/hook/package/Pages reference, transfer action, smoke test, and recovery action. Explicitly verify absence where appropriate; App installation access does not establish deployment coverage. Keep credential values and sensitive callback paths outside Git.
- Record the owner's access and billing decision: do not retain
fhemmerreliasaccess after transfer and do not purchase another seat. APIcollaborators?affiliation=directreturns[], repository teams are[], and both accounts are source organization owners. The owner access page confirms zero direct grants. The earlier extra-seat warning incorrectly treated effective source-owner access as a direct collaborator. No additional license is required for the observed grants; verify the destination access and seat count after transfer, and stop if GitHub presents an unexpected billing change. - Verify destination plan support, organization Actions/runner policy, effective protections and credential access, plus the required CLI/App authorization scopes. Resolve every unknown or conflicting mapping before cutover. Any additional billing purchase remains an owner action.
Acceptance Criteria
- Transfer all 65 in-scope source repositories using the collision mapping, preserving repository IDs, Git history, issues/PRs, releases, visibility, and archive state. Refresh the source inventory before declaring completion.
- Transfer the owned SFL App registration, verify App/client identity and permissions after transfer, and configure its organization installation and repository coverage. Check transfer warnings and recover any installation disruption.
- Install/connect native Codex for all current/future organization repositories. Verified installation168678981 and a clean fixed-head private organization smoke review at
f225d94d49a5951d6b2b205ad08990337aff040f. SFL registered gate/runtime proof remains in Replace repository SFL deployments with an organization App and hs-buddy pilot #139. - Reconcile collaborators/teams, branch protections/rulesets, Actions policies/runners, environments, variables/secrets, deploy keys, webhooks, and App access. Verify retained settings rather than assuming every integration migrates automatically.
- Update active references across transferred repositories and external deployments: workflow/reusable action URLs, packages/GHCR, Pages/custom domains, release consumers, repository badges, local remotes, credentials, and scripts.
- Retain a recovery log and old repository redirects. Keep both legacy accounts; do not delete fhemmer or the personal account as part of this task.
Definition of Done
- Record a per-repository before/after result and integration smoke-test outcome, including any concrete blocked transfer and its follow-up.
- Complete the new-source release and installer verification prepared by the tooling issue. Update repository instructions and infrastructure references.
- Exactly 65 source IDs are verified at their mapped destinations. The two owner-approved retained IDs remain in HemSoft with their original privacy/archive state. Account for all 67 baseline IDs without reporting retention as transfer.
Validation
- Compare paginated
gh api user/repos?affiliation=ownerandgh api orgs/fhemmer/reposinventories withgh api --paginate 'orgs/ORG/repos?per_page=100', using the same authenticated account. Match source IDs to destinations exactly once. - Fetch each destination's metadata, refs, releases, issue/PR counts, and relevant settings; compare them with the recorded baseline. Test Git fetch using
github-personal1and the destination URL. - Run representative CI, package/site/deployment checks, SFL App token operations, and a native Codex review after cutover. Document archived repositories without unarchiving them.
- Follow GitHub repository transfer behavior and App ownership transfer; verify redirects, Pages/package differences, and installation access explicitly.
Owner access decision (2026-10-06)
Franz selected: Remove fhemmerrelias access after transfer. Do not revoke source organization membership before transfer, grant destination access, or purchase an additional seat.
- Distinguish inherited source-owner access from direct collaborator grants.
fhemmeris an organization;fhemmerreliasand HemSoft are its active owners. There are zero direct collaborators and zero repository teams.fhemmerreliasis not a hemsoft-dev member. - Record the observed billing assessment: no retained direct collaborator requires a new seat. Source organization ownership does not grant access to hemsoft-dev; the destination organization's permissions apply after transfer. The transfer preparation page selected hemsoft-dev without a billing warning; its confirmation field was left empty and nothing was submitted.
- After transfer, verify
fhemmerreliaseffective access is revoked and the destination license count remains one. Remove any unexpected direct destination grant only after checking its billing/access state.
The earlier $4/month warning was based on effective admin access, not a retained direct grant; this owner/API evidence corrects that interpretation. Other mandatory pre-transfer gates remain open.
Fresh owner/runtime evidence
- Fresh read-only source capture still enumerates all 67 IDs, 25 private and 14 archived repositories. The original 142 unverified endpoint results remain visible.
- Runner queries for all 67 repositories and credential-name queries for all 16 environments completed successfully, 99 reads total. Only HemSoft/yahtzee has runner mini-github-runner-01, online and idle. All 32 environment secret/variable name lists are empty. The destination has no self-hosted runners and its Default group excludes public repositories. Recheck immediately before cutover.
- Three Vercel-connected source repositories are private: now-leadership-group, set-it-free-loop-site, modern-web-stack-poc. Their Hobby workspace cannot continue Vercel Git deployments from private organization repositories; Franz selected retirement of the modern-web-stack-poc Vercel project, while retaining its GitHub repository. Record retirement and associated Supabase resource treatment before clearing that provider gate. Franz directed that now-leadership-group and set-it-free-loop-site remain private in the personal HemSoft account. This avoids the private-organization Hobby restriction, with no Pro purchase. Cloudflare owner DNS now confirms proxied apex A 76.76.21.21 and www CNAME cname.vercel-dns.com, matching the Vercel project domain bindings. Cloudflare provides DNS/proxy; Vercel is the configured website origin. Preserve both hosting projects. set-it-free-loop-site remains archived. No project has been deleted or plan purchased.
- Production domain GETs succeeded for nowleadershipgroup.com, www.hemmer.us, dashboard.hemmer.us and poc.hemmer.us. setitfreeloop.org had no resolvable address before transfer; retain that existing failure rather than attributing it to migration. Credential validity and non-Vercel provider resources/absence remain pending.
Supplemental records are in PR143. These observations do not waive the all-gates-before-any-transfer requirement.
Additional owner/reference observations
- Supabase: sole Owner franz_hemmer@hotmail.com, Free organization with two paused projects. One is connected to Vercel dashboard. modern-web-stack-poc references a different public Supabase project hostname, not either visible project; the later owner confirmation below records that repository as unused, with no database deletion authorized. No database resume, deletion, backup download or credential read.
- Blacksmith: fhemmer owner dashboard reports zero October jobs/minutes/spend and no payment method/invoices. This is a reporting-period observation, not global historical absence.
- Source scan: 65 complete default-branch trees; original fhemmer404 and n8n-workflows409 remain unverified. All100selected workflow/manifest blobs were read successfully, 96workflowfiles. buddy-ios has a root-only legacy review-tier manifest; hs-buddy has canonical full-tier. Preserve existing configurations and resolve runtime migration deliberately.
- Private SFL App installer offers only HemSoft. Organization installation requires the gated App ownership transfer; no public-visibility workaround, key read or transfer performed.
These observations remain supplemental evidence in PR143, not completion of the mandatory integration ledger.
Owner retention decision
Franz's recorded decision retains HemSoft/now-leadership-group, ID1162179521, and HemSoft/set-it-free-loop-site, ID1169698740. Fresh metadata confirms both remain private and the site repository remains archived. Keep the sealed original 67-ID inventory; the execution scope is 65 transfers and 2 retained sources. Exclude these two from organization SFL rollout. Retention does not waive checking whether App ownership transfer affects their existing personal installation.
Private App transfer warning
The authenticated Advanced transfer preparation, selecting hemsoft-dev Organization, explicitly warns that the private App will be automatically uninstalled from the personal account when transfer completes. Confirmation remained empty, submission disabled, and no transfer occurred. Reconcile the 64 selected personal repositories and the two retained website repositories before App ownership transfer. Their complete default-branch trees contain no workflows or SFL manifests, which does not prove that no external webhook/client depends on the App. Preserve visibility; do not make the App public as a workaround.
Retained App dependency verified
- Franz confirmed that neither retained website uses the private SFL App outside workflows and its remaining credentials are unused. The automatic personal-installation removal therefore has no identified retained-site runtime dependency. Preserve both sites and their personal repositories.
This resolves only the shared-App dependency of the two retained sites. Other applicable mandatory gates, including actual provider/credential reconciliation for the 65 transfer targets, remain open. No credential value was read or removed and no App transfer was submitted.
Provider usage absence verified
- Franz confirmed that none of the 65 transfer targets uses Azure Pipelines, Fly.io or Railway. These three usage candidates are cleared; no further Azure sign-in is needed. Captured App scopes remain historical evidence. Other known providers, credentials, references, runner readiness and App cutover gates remain mandatory.
Owner-confirmed unused legacy repository credentials
- Franz confirmed that the unreferenced legacy SFL_APP_PRIVATE_KEY and OPENROUTER_API_KEY repository Actions entries on the 42 scanned transfer targets are unused by external clients. PR143 records the exact repository IDs and names. Keep encrypted entries in place; no value retrieval or validity test is needed for these unused dependencies.
Actively referenced credentials in buddy-ios, hs-buddy and the SFL source, unrelated credential names, and provider environment variables remain separate checks. This clears only the named unused dependencies, with all other mandatory gates still required before any source or App transfer.
Owner external-resource scope and unused project treatment
Franz confirmed only inventoried external resources are used by the 65 transfer targets, with no Blacksmith usage. He also confirmed modern-web-stack-poc is unused. Its Vercel Git connection was removed and a settings reload confirms the project is not connected to a repository. Project settings/configuration/history and database data remain preserved; no purchase or project/database deletion occurred. The old Supabase hostname returns DNS NXDOMAIN; no active integration is required for this unused repository. PR143 records both scoped receipts and preserves the known Vercel project resource ID. Active credentials and all other mandatory pre-transfer gates remain separate.
Current dependency evidence (October 6 continuation)
- Authorize organization users to request SFL PR reviews #137 is closed with real fixed-head registrations, native clean results and strict Actions gates in both organization pilots on immutable rc.15. Repeat sync is a no-op. This proves the legacy-owner bridge; final canonical source/App-transfer rollout remains pending. Negative authorization/context cases are explicitly workflow fixtures, with live unregistered native reviews unable to clear the failing gate and registered requests setting pending before success.
- hs-buddy PR763 prepares the trusted review controller for its immutable repository ID under the new owner. Current
a7c05d2has a clean native review and all required CI, including benchmark and aggregate CI, passing. The owner approved this preparation merge and its read-only checks. The preparation PR has merged; post-transfer runtime gates remain separate. - Reports issue62 and PR63 prepare multi-owner collection, cache invalidation and canonical report links. Current
e5c05ddhas a clean native review, current-head screenshots/recording and all CI passing. Local 97 units, 48 pre-rebase serial browser tests, current canonical-link browser validation, risk and 95.64% qualified mutation pass. The owner approved this preparation merge and its read-only checks. The preparation PR has merged; post-transfer runtime gates remain separate. The merged Reports main passes CI. Its owner-approved replacement passes the read-only credential check, verifying HemSoft/classic repo scope and private organization access. Reports issue62 is complete; this preparation credential gate is cleared. No token was printed or persisted. - Earlier PR143 preparation added durable observer run/attempt/check/workflow identity, exact final visibility and independently signed release-asset verification. The current preparation revision and review state are recorded below. Updated execution metadata requires the next canonical release and fresh live runtime evidence. Main-only source credential verification and fresh all-owner pre-cutover reconciliation remain mandatory.
No source repository or owned App has transferred. The sealed67-ID baseline,65 transfer targets,2 retained personal repositories,privacy/archive settings and one-seat decision remain in force. The Reports main-only credential check is complete. Main-only owned-App verification, active credential treatments, provider continuity and fresh App selection proof still require their individual receipts. Organization Actions governance APIs now succeed after the owner scope refresh: all repositories/actions enabled, default workflow permission read, workflow review approvals disabled, zero organization secrets/variables, and Default runner group excludes public repositories. No policy or organization secret has been changed.
Fresh read-only checks — October 6, 11:12 PM EDT
- The 67-source-ID GitHub refresh matches the sealed names, visibility and archive state: 25 private and 14 archived baseline repositories. The 65-transfer/2-retained mapping is unchanged. Original unavailable endpoint classes remain visible.
- Fresh runner/environment queries completed all 99 reads successfully: only yahtzee runner 21 is registered, online and idle; all 16 environment secret/variable name inventories are empty. No values were read.
- Destination API reconfirms Team, one filled/purchased seat, active HemSoft owner access and native Codex installation 168678981 with all-repository access. Owned SFL App 4448946 remains under HemSoft with its approved public client identity and permission set.
- Authenticated owner settings reconfirm no fhemmer classic protections or rulesets. The owner reports SFL installation150383874 now selects all repositories. The shared browser still requires sudo mode; a fresh GET-only workflow metadata capture must verify the saved setting. Preserve the original selected snapshot.
- Fresh owner-provider GETs reconfirm five Vercel projects, with modern-web-stack-poc disconnected and all production targets READY. The two retained personal connections are unchanged. Dashboard has a pre-existing failed preview; that is preserved as baseline evidence. Cloudflare still has the exact proxied apex A/www CNAME, no zone Worker routes, and the existing nlg-contact-form Worker deployment unchanged. These metadata checks do not establish database/model credential validity.
No transfer gate is cleared solely by these metadata reads. The owner confirms the dashboard database is unused and must remain paused with its configuration. No resume, deletion or database query is authorized. Active workflow credentials and the remaining App/settings verification still need their named receipts.
The approved hs-buddy preparation now passes all main CI and release qualification. Its unchanged, already published version was correctly not republished. Owned preparation branches/worktrees are cleaned up. Source App verification remains mandatory. The Reports replacement check passed and its preparation issue62 is closed.
The existing hs-buddy controller run at merged main 2e7fd041 successfully minted its scoped App token and reconciled its configured state. Auto-merge remains disabled. This clears current App-key authentication for that controller, while model credentials and post-transfer runtime remain separate. Source public App ID/client variables match the approved identity. Dashboard Fetch News is currently disabled_inactivity; preserve that state and its configuration, with no database query or cron invocation.
Fresh destination provider observation: authenticated organization GET now confirms Vercel installation168725517, App8329, all-repository selection and no suspension, created October6 at11:33PM EDT. This supersedes the earlier not-installed preparation observation. No installation/selection change was made in this continuation. Actual dashboard and landing-project repository binding, permitted hosting and post-transfer continuity remain mandatory.
Mandatory current source and provider evidence
Before any repository or App transfer, capture a fresh full reference scan of all 67 sources, read every workflow/SFL manifest/provider configuration at its immutable revision, reconcile the credential/provider ledger and repeat each default head, tree and complete branch list. Changes require a new scan and reconciliation; preserve the sealed historical 67/142 evidence.
Run the owned-App credential check on current source main after that scan and complete source refresh within 15minutes of its successful completion. Destination installation evidence must include the approved granted permissions.
Provider success requires resource-specific successful GETs and primary observation times. Verify expected Vercel Git bindings, READY production and preserved aliases; preserve the retired Git connection, current preview failure, retained hosting and paused Supabase configuration. Verify actual Pages URLs, Cloudflare DNS/proxy/Worker/subdomain/routes and runner registration after the relevant transfer/destination observations.
Preparation PR #143 is now at ec24a6520e60ec0b6418c132262a6825ae21d016. All 284 migration tests pass. Four invalid records accepted at6b250fc now fail, and a valid edited owner approval rejected at that head now passes. Five native findings are resolved. New guards require concrete repeat-command execution, complete fresh environment and secret-name GETs, complete source policy within60seconds before each transfer, effective edited approval times and exact registered-review compare GETs. The one fresh Codex request and current CI contexts remain under verification. Historical branch-only evidence covers124heads/326files; complete branch/tag scanning, historical credential-reference reconciliation and current Windows resource/protection reconciliation remain mandatory before cutover. No transfer gate is cleared by these preparations.
Preservation-only outcomes apply solely to the two owner-approved unused resources and still require exact successful provider metadata GETs. Modern-web-stack-poc Git retirement remains complete, but its older summary-only preservation receipt is now honestly marked partial until fresh metadata replaces it. Preserve its project/configuration/history and the paused dashboard database/configuration. Approved recovery requires the actual owner-authored resource decision and independently successful provider state.
Active credential check preparations
hs-buddy #765, Buddy iOS #35, dashboard #25, and gh-x #202 now pass required CI and have clean exact-head Codex receipts with no unresolved findings. They add owner-dispatched, main-only GET checks and 19 committed synthetic tests per repository. Dashboard's existing Vercel preview error remains disclosed. A late Buddy SFL claim about a literal masked authorization header did not reproduce against committed code and was resolved with synthetic outbound-header evidence. These four new external merges and actual credential checks await owner approval; the existing approval for hs-buddy #763 and Reports #63 does not cover them. Credential validity remains pending until the trusted main checks succeed.
October 7 fresh runner and credential inventory
Fresh owner GETs across all 67 sources completed 134 successful raw secret/runner pages. All 98 repository secret names match the sealed inventory. The current runner set has changed.
- Reconcile and preserve survival-shelter-opus55 repository ID1399232444 runner ID10,
DESKTOP-7ES73Q4, Windows/X64 withue5.7, plus its newUE_RUNNER_ENABLEDvariable and active main ruleset24630478. Read-only laptop checks confirm its foreground listener, exact non-secret.runneridentity, and enabled running logon taskGitHub Actions runner - HemSoft-survival-shelter-opus55invoking the existingrun.cmdin its runner directory. There is no Windows service. Preserve this startup mechanism, current human work, and the ruleset's deletion/non-fast-forward restrictions andBuild and simulation testsrequirement. Existing main CI37691869137 succeeded on runner10; verify current readiness and destination registration/startup/job continuity at transfer. - Reconcile yahtzee runner ID21,
mini-github-runner-01, into the final fresh ledger before transfer. The kernel OOM log explains the earlier offline state. Its existing VM was restarted without configuration or registration changes; strict SSH confirms active/enabled service, GitHub confirms online/idle identity, all six isolation probes pass, and fresh smoke37696456923 succeeded on runner21. Verify stable capacity/current readiness at cutover and destination continuity afterward.
These are mandatory pre-transfer resource gates. The inventory refresh made no runner changes. A later recovery restarted only the existing crashed yahtzee VM and dispatched its verified manual-only, zero-permission smoke; no registration or isolation configuration changed. The historical 67-repository/142-unavailable-endpoint baseline remains sealed. New classic-protection lookup404s on current branches and an initialized repository remain visible in the separate refresh; destination Actions authorization is now available.
Activity
HemSoft commentedon Oct 6, 2026
Owner verification update, October 6, 2026:
f225d94d49a5951d6b2b205ad08990337aff040f. Organization App installation168678981 selects all current/future repositories. This verifies the connected review flow; SFL registered gate and intended runtime proof remain separate.PR143 records the ledger, rollout matrix and supplemental evidence. None of the 67 source repositories or the SFL App has been transferred.
HemSoft commentedon Oct 7, 2026
Owner scope decision, October 6, 2026: Franz directed that HemSoft/now-leadership-group and HemSoft/set-it-free-loop-site remain in the personal HemSoft account to avoid the private-organization Vercel Hobby restriction. Exclude these two repository IDs from transfer and organization SFL rollout; preserve their existing privacy, archive state, integrations, and hosting. The sealed original inventory still contains 67 IDs; the execution plan is now 65 transfers and 2 retained sources. No Vercel Pro purchase is selected. modern-web-stack-poc still transfers, with retirement of only its Vercel project recorded separately. Cloudflare owner sign-in is now available, and live origin verification is in progress. No source repository or owned App has been transferred.
HemSoft commentedon Oct 7, 2026
Franz confirmed that neither retained repository uses the private SFL App outside GitHub workflows, and the remaining SFL credentials are unused.
This resolves the retained repositories' shared-App dependency verification for the private App's automatic personal-account uninstall warning. Keep HemSoft/now-leadership-group and HemSoft/set-it-free-loop-site at their existing personal locations, preserving privacy, archive state and hosting. No credentials were read, removed or copied, and no App transfer occurred. All other applicable mandatory pre-transfer gates remain required.
Machine-readable record of the same previously confirmed owner fact. This adds no new permission or scope.
HemSoft commentedon Oct 7, 2026
Owner confirmation: none of the 65 approved repository transfer targets currently uses Azure Pipelines, Fly.io or Railway. Franz supplied this explicit fact on October 6, 2026.
This resolves those three provider-usage candidates. Captured installed App access remains in the historical inventory and candidate columns; it is not treated as evidence of active resources. No further Azure sign-in or project identification is required for this absence confirmation.
This receipt does not waive the other mandatory pre-transfer gates, including known Vercel/Supabase/Blacksmith resources, the yahtzee self-hosted runner, existing credential validity, repository references, or owned SFL App cutover readiness. No repository or App has been transferred by this confirmation.
Machine-readable record of the same previously confirmed owner fact. This adds no new permission or scope.
HemSoft commentedon Oct 7, 2026
Franz confirmed that the legacy SFL_APP_PRIVATE_KEY and OPENROUTER_API_KEY entries with no references in the scanned default-branch workflows on the 42 identified transfer targets are unused by external clients.
Classify only those unreferenced legacy entries as owner-confirmed unused. Keep encrypted entries in place; no credential values need to be retrieved or tested for these unused dependencies. Actively referenced credentials in buddy-ios, hs-buddy and the SFL source, and unrelated dashboard/gh-x/reports/skills credentials, remain separate checks. This does not waive other mandatory pre-transfer gates or authorize a source/App transfer before they pass.
Machine-readable record of the same previously confirmed owner fact. This adds no new permission or scope.
HemSoft commentedon Oct 7, 2026
Franz confirmed that the 65 transfer targets use only the inventoried Vercel, Cloudflare, Supabase, GitHub Pages and yahtzee runner resources, with no actual Blacksmith usage. Captured App installations remain historical candidate evidence. This owner fact supports explicit absence for other external providers, while actual resource, credential and GitHub workflow/reference gates remain separate.
Franz also confirmed that modern-web-stack-poc is unused. Its historical Supabase hostname krdpxbpnvemzfxbnkgcq.supabase.co is absent from the accessible owner dashboard; independent system DNS and public DNS return no such host / NXDOMAIN. No database was queried, resumed, deleted or otherwise changed. Preserve any database data untouched while retiring the unused Vercel integration and transferring its GitHub repository.
Machine-readable record of the same previously confirmed owner fact. This adds no new permission or scope.
HemSoft commentedon Oct 7, 2026
Franz confirms dashboard-linked Supabase project
cevpnetigzotgstxxjpmis unused. Preserve its paused state, database data and existing configuration. This resolves its active-versus-unused treatment only; no database resume, deletion, query, backup download or credential-value read is authorized or performed. Preserve the separately captured account-owneddashboard-recoveryresource as well; no repository association is inferred for it.Other mandatory pre-transfer gates in #138 remain in force.
HemSoft commentedon Oct 7, 2026
Owner update: HemSoft reports that SFL App installation 150383874 has been changed to all repositories. Preserve the original selected-repository snapshot as historical evidence. Fresh automated verification of the saved repository selection remains mandatory before transfer. The shared settings page still requests sudo-mode confirmation; the CLI installation repository-list endpoint returns HTTP 403. The reviewed GET-only App credential workflow will capture current installation metadata without exposing credential values or minting an installation token. No repository or App transfer is authorized by this settings update alone.
HemSoft commentedon Oct 7, 2026
The owner-approved existing HemSoft CLI credential was copied securely to
REPORTS_PATthrough a subprocess pipe; no credential was printed or persisted. The write occurred before the separateadmin:orgrefresh and enforced the disclosed scope contract (repo,workflow,read:org,user,gist,admin:public_key).The reviewed, unchanged main-only GET check now passes: https://github.com/HemSoft/reports/actions/runs/37569272374 at
776539e9f8b66d1e001d4cca3b45117aa96cdd41. It verifies HemSoft identity, classic repo scope, source ID1358408598 and private organization pilot ID1408025382. Changes since preparation merge bb89a466 affect only unrelated Dune editor files; the credential workflow is unchanged.Preparation PR #63 is merged and its required live credential verification is complete. Repository/App transfers and post-transfer provider continuity remain governed by source transfer issue #138.
HemSoft commentedon Oct 7, 2026
Vercel pre-transfer preservation captures now match all five existing project IDs, Git links, production/preview deployments and domain bindings. The retired modern-web-stack-poc connection remains absent, the two retained personal repositories remain connected, and dashboard's existing failed preview remains unchanged. No deployment, project, billing plan or connection was mutated.
The two public transfer targets, dashboard and hs-landing-page, can use Hobby after the organization move under Vercel's current public-repository policy. Current Git documentation limits the organization restriction to private repositories. Vercel staff's explicit clarification confirms that public organization repositories and new projects are supported; the general limits page retains older broad wording. This supports the existing public-transfer plan without a Pro purchase, but does not count as actual destination installation or post-transfer reconnection proof.
Preserve both existing projects and configuration. After their exact immutable repository IDs move, grant Vercel selected access to those two repositories and reconnect the existing projects; do not create replacements, reconnect the retired project or grant every organization repository. Existing production resources remain the recovery baseline. Actual post-transfer continuity remains mandatory.
HemSoft commentedon Oct 7, 2026
The unchanged, owner-approved Reports GET-only credential workflow passed again after the separate CLI admin:org refresh: run37573322165, current Reports main7ad1d1e61052a43ff67851cc4b35942796f621e4. Its workflow blob matches the reviewed preparation merge. This verifies the stored HemSoft/classic repo-scope contract still works; no token was printed, copied again or replaced. New human Reports changes remain untouched. This is pre-transfer proof; post-transfer verification remains mandatory.
HemSoft commentedon Oct 7, 2026
The owner approved and all four preparation PRs merged: hs-buddy #765, Buddy iOS #35, dashboard #25, and gh-x #202. Each had fresh exact-head required CI, clean connected Codex review and zero unresolved threads before its guarded merge. Human work was preserved and the preparation branches/worktrees were cleaned.
Trusted-main read-only authentication passes for hs-buddy OpenAI, Buddy OpenRouter, Buddy SFL App identity/install/permission ceiling, and dashboard GitHub token. Their allowlisted metadata and actual artifact/server digests were verified. Dashboard's intervening automatic version bump changed only src/lib/version.ts; verification workflow/script blobs still match its reviewed PR.
gh-x's original CODEX_REVIEW_TOKEN check reported
identity_or_accessbecause the new PowerShell parser lost its array shape for an empty or single OAuth-scope response. Approved repair #204 merged at12b77dda42691f575292f05223248750b00e2344. The corrected main-only, GET-only check passes with the unchanged secret. Its downloaded artifact verifies HemSoft identity, a successful repository metadata GET and the actor's repository write role. OAuth scope isunreported; token write grants and post-transfer access are not verified by this read-only check. gh-x remains HemSoft/gh-x. No credential was copied or replaced. Isolated merge and cleanup preserved the other agent's checkout and worktrees. v0.18.2 is published, with all12serverdigests and cryptographic source/signer attestations verified. Final inherited changelog CI and isolated synchronization remain separately verified delivery work. Historical tag-only credential references still require mandatory reconciliation; successful authentication alone does not clear transfer readiness.These GET checks prove authentication and the stated App metadata only. They do not prove model runtime, fine-grained token write grants, post-transfer access or final resource continuity. The baseline dashboard Vercel preview error and Buddy optional SFL failure remain visible. Source/App transfers remain gated. Main CI and any inherited release delivery are still being verified.
All four prior preparation deliveries completed successfully. Their GET-only credential checks passed after the gh-x parser correction. Full branch/tag reconciliation, current environment inventories, Windows runner/main-policy reconciliation, final fresh readiness and post-transfer access/continuity remain required.
HemSoft commentedon Oct 8, 2026
Owner changed the delivery order on October 7: move the repositories to hemsoft-dev first, then handle all SFL work there. This supersedes the pre-transfer SFL App, organization credential, and reviewer/runtime prerequisites. No App-key sealing or organization credential write is authorized by this change.
The repository transfer scope remains 65 mapped transfers, with now-leadership-group and set-it-free-loop-site retained in personal HemSoft. Preserve privacy, archive state, refs/history, existing hosting, paused databases and runner registrations. Keep the fhemmer collision mapping and verify fhemmerrelias has no private destination grant.
SFL App ownership, credential delivery, canonical source/release reconciliation and organization reviewer rollout stay open under #136/#139 after the repository move. Transfer and resource preservation receipts will be recorded here; SFL preparation is no longer a reason to hold the repository transfers.
HemSoft commentedon Oct 8, 2026
Repository move completed on October 7, following the owner's repository-first direction.
SFL App ownership, organization credentials, canonical release/source reconciliation and reviewer rollout remain deferred under #136/#139. No App-key sealing, App transfer or organization credential delivery was performed. This issue stays open for the separately deferred SFL App scope; the repository-transfer portion is complete.
HemSoft commentedon Oct 8, 2026
SFL App ownership transfer is complete. GitHub accepted transfer 66896 to hemsoft-dev; App ID 4448946, client ID Iv23liwvwJJUh2bUIKLW, existing private key and permission ceiling are preserved. The private App is installed for all current and future organization repositories as installation 169090497. The main-only GET-only credential check passed using the existing source repository key: https://github.com/hemsoft-dev/set-it-free-loop/actions/runs/37721429180 . No key rotation, sealing export or organization secret creation occurred. All 65 repository transfers were already verified in the preceding completion receipt. Issue #139 still tracks reviewer rollout and governance; remaining migration evidence reconciliation stays visible here.
HemSoft commentedon Oct 8, 2026
Evidence correction from PR148 review: the fhemmer repository's ID, refs, privacy, archive state, default branch and destination policy are verified, but fresh source-policy preservation is not fully established. Its Free-plan source ruleset API returned403 at cutover; the actual owner-browser empty-policy capture was from October7 at13:31EDT, several hours earlier. No immediate pre-transfer browser capture was attached. A retrospective owner-browser audit search shows only transfer and integration removal events for October7 onward; its coverage cannot replace a fresh capture. PR148 now explicitly records this historical limitation and links both actual captures. This corrects the earlier blanket policy-preservation claim without changing the verified65 repository transfers or reviving superseded SFL pre-transfer gates.
HemSoft commentedon Oct 10, 2026
Closing the remaining SFL project backlog under Franz’s instruction to freeze and remove SFL. The repository transfers are historical completed work. This closure does not waive or claim verification of the documented fhemmer protection-preservation evidence limitation; that limitation remains recorded here. The SFL App is now uninstalled and SFL integrations are being retired.