Skip to content

Keep Colony branding consistent across install paths#22

Merged
NagyVikt merged 1 commit intomainfrom
agent/codex/colony-readme-branding-2026-04-24-02-09
Apr 24, 2026
Merged

Keep Colony branding consistent across install paths#22
NagyVikt merged 1 commit intomainfrom
agent/codex/colony-readme-branding-2026-04-24-02-09

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by gx branch finish (PR flow).

The stale Guardex lane already held the README, license, package namespace, docs, scripts, imports, runtime paths, and tests needed for the Colony identity. Commit them together so the CLI, MCP server, workspace packages, and examples present one installable surface instead of a split cavemem/Colony story.

Constraint: Finish existing Guardex worktree agent/codex/colony-readme-branding-2026-04-24-02-09 without reopening the migration scope

Rejected: Commit README and license only | package metadata and runtime paths would remain inconsistent with the public Colony surface

Confidence: high

Scope-risk: moderate

Directive: Do not rename package/import surfaces again without checking the published package and registry plan

Tested: pnpm -r typecheck

Tested: pnpm -r test

Tested: pnpm lint

Tested: git diff --cached --check

Not-tested: npm publish or registry install
@NagyVikt NagyVikt merged commit eb4dad9 into main Apr 24, 2026
@NagyVikt NagyVikt deleted the agent/codex/colony-readme-branding-2026-04-24-02-09 branch April 24, 2026 00:23
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.

1 participant