Skip to content

Licence holder is Agente Labs - #25

Draft
AgenteLabs wants to merge 1 commit into
mainfrom
holder-agente-labs
Draft

AgenteLabs wants to merge 1 commit into
mainfrom
holder-agente-labs

Conversation

@AgenteLabs

Copy link
Copy Markdown
Owner

The copyright holder for this estate is now Agente Labs. The register change is AgenteLabs/flashyos#246.

Changed (licence-holder statements only)

  • LICENSE:189: Copyright (C) 2026 Flashy Labs -> Copyright (C) 2026 Agente Labs. The licence body is untouched.
  • CONTRIBUTING.md:74: Apache-2.0, © 2026 Flashy Labs -> Apache-2.0, © 2026 Agente Labs.

Tests (before / after, identical)

  • npm test: 28 files passed, 294 passed, 1 skipped.
  • npm run lint: clean.
  • npm run test:standalone: 47 tests, 39 pass, 0 fail. The rest are skipped, probably because dist is not built in the worktree.

No test asserted the old holder string, so none was edited.

Left alone

  • CONTRIBUTING.md:3: "part of the Flashy Labs estate". This is a brand/estate description, not a licence holder.
  • DEVLOG.md and *.fragment.json: generated or historical.

Generated by Claude Code

The copyright holder for this estate is now Agente Labs (register change: AgenteLabs/flashyos#246). Only licence-holder statements change: the LICENSE copyright line and the CONTRIBUTING.md licence line. The licence body is untouched.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V

Copy link
Copy Markdown
Owner Author

Dependency audit is red, but not because of this PR. The log shows npm audit reporting 4 advisories (3 moderate, 1 high) in dev dependencies: vite 8.2.0–8.2.2 and vitest/@vitest/mocker/@vitest/coverage-v8. This PR only changes the LICENSE copyright holder and the register-matching text, so it doesn't touch the lockfile or any dependency. The advisories are new upstream and would fail any branch of this repo. npm audit fix is available, but a dependency bump isn't part of this change, so I'm not widening the PR; it should go in its own PR (lockfile regenerated with npm 10.9.8 per the repo's rules). I haven't re-run the job, since it would read the same advisories.


Generated by Claude Code

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