Skip to content

Rename sweep: FlashyLabs is AgenteLabs - #21

Draft
AgenteLabs wants to merge 5 commits into
mainfrom
rename-sweep
Draft

AgenteLabs wants to merge 5 commits into
mainfrom
rename-sweep

Conversation

@AgenteLabs

Copy link
Copy Markdown
Owner

Summary

  • Rewrites the github.com/flashylabs/… paths in the README and the reusable-workflow uses: references in backlog.yml and secret-scan.yml (GitHub does not redirect those after an owner rename — this is why secret-scan has been red here) to AgenteLabs. Produced by tools/estate-rename-sweep.mjs --fix from AgenteLabs/flashyos#229.
  • Left as-is by design: @flashylabs/rails ×2 in the README (no published successor on any registry), @FlashyLabs/ledger-owners in docs/entry-hash.md (a CODEOWNERS-style team handle, not a package — rename by hand when the team exists under AgenteLabs), and CLAUDE.md.
  • Not in this PR: the GitHub repository description still says npm install @flashylabs/ledger — that is a settings write the session's proxy refuses; one edit in the repo's About box.

Test plan

  • git diff reviewed: README + two workflow files
  • CI on this branch

Generated by Claude Code

The GitHub owner was renamed and these clone commands, badges and
manifest fields still pointed at an owner that 404s. Rewritten by
tools/estate-rename-sweep.mjs in flashyos (--fix); packages with no
published successor and prose are reported and left as they were.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
tests/workflow-pins.test.ts exempts first-party reusable workflows from
SHA-pinning by owner; the first sweep moved the uses: lines to
AgenteLabs and left the exemption on FlashyLabs, so the test refused
the estate's own convention. Rule and prose move together now.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
The rename sweep moved the owner in flashyos.roles.json and left its
served twin behind, which the frontdoor job catches (diff -q). Nothing in
this repository produces the served copy, so it is copied byte-for-byte
from the root, which is what the job asserts.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
…file

The Dependency audit job is red on main on four advisories, all in the
test toolchain:

  @vitest/mocker  GHSA-qxg6-89mg-rqv8, GHSA-xp26-3454-mjgp (moderate, <=4.1.11)
  vite            GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw and four more
                  (high, 8.2.0 - 8.2.2)

vitest and @vitest/coverage-v8 move one patch, to ^4.1.12, the first
release whose mocker is patched; vite is a transitive dependency and the
lockfile now resolves it to 8.3.5, inside vitest's own range. Lockfile
regenerated with npm 10.9.8 (Corepack, as packageManager declares);
`npm audit` reads 0 vulnerabilities and `npm run check` (typecheck, lint,
coverage, standalone) passes. CHANGELOG and RELEASES untouched: nothing
shipped changes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
(cherry picked from commit 7d0f51e)
CHANGELOG, RELEASES and README quote versions published under
@flashylabs/ledger; they are a record kept in tense, not a reference to
the owner, and the sweep had rewritten the name in them.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants