chore: rename project to Hex Zero

[christopherjnelson]

Summary

• rename the product and repository-facing metadata from Agentborne to Hex Zero
• move all workspace packages, imports, filters, and lockfile references to @hexzero/*
• introduce canonical HEXZERO_PROVIDER, HEXZERO_EXPERIMENT_DB, .hexzero/experiments.sqlite, hexzero browser keys, and hexzero-experiment- downloads
• preserve legacy environment, archive, browser-storage, and schema-v9 export compatibility without changing gameplay, prompts, telemetry meaning, scheduling, maps, providers, or UI structure

Renamed files and identifiers

No source directories were renamed. Updated identifiers include:

• root package: agentborne → hexzero
• workspace packages: @agentborne/{game-api,world-lab,agent-runtime,experiment-archive,shared,world-engine} → @hexzero/*
• all TypeScript imports, pnpm filters, scripts, Next.js transpile-package entries, Playwright commands, and lockfile dependency keys using that scope
• product prose/metadata: Agentborne → Hex Zero
• source repository metadata: BlackSwampAI/agentborne → future BlackSwampAI/hexzero
• canonical provider selector: HEXZERO_PROVIDER
• canonical archive selector: HEXZERO_EXPERIMENT_DB
• default archive: .hexzero/experiments.sqlite
• browser storage: hexzero.world-lab.{follow-turn,run-target,unattended-recovery,activity-dock}
• mutation header: X-Hexzero-Mutation-Id
• download prefix: hexzero-experiment-

Contract identifiers text-flat-json-v3, durable-influence-v2, export schema version 9, database migrations/tables, experiment IDs, agent IDs, event IDs, note IDs, and raw export contents are unchanged.

Compatibility

• HEXZERO_PROVIDER takes precedence over deprecated AGENTBORNE_PROVIDER; legacy selection warns without exposing values.
• HEXZERO_EXPERIMENT_DB takes precedence over deprecated AGENTBORNE_EXPERIMENT_DB; legacy selection warns without exposing values.
• archive resolution is CLI --db, canonical environment, legacy environment, existing canonical default, existing legacy default, then new canonical default.
• existing .agentborne/experiments.sqlite is opened in place and is never moved or overwritten automatically.
• valid legacy browser settings migrate idempotently to canonical keys; malformed values cannot bypass validation.
• existing agentborne-experiment-*.json schema-v9 exports remain importable unchanged.

Final agentborne allowlist

Every case-insensitive occurrence was reviewed. Remaining occurrences are limited to:

• .env.example: documented deprecated environment aliases and legacy archive example
• .gitignore: ignored legacy .agentborne/ archive artifacts
• README.md: one formerly-Agentborne note plus environment, archive, export, and browser-storage compatibility guidance
• docs/EXPERIMENT_ARCHIVE.md, docs/SECURITY.md, and docs/TESTING.md: compatibility, migration, ignore, and test documentation
• apps/game-api/src/app.ts and server.ts: legacy provider alias fallback and deprecation warning
• apps/game-api/src/app.test.ts: legacy provider compatibility regression coverage
• packages/experiment-archive/src/database.ts and cli.ts: legacy environment/default-path fallback and migration notice
• packages/experiment-archive/src/archive.test.ts: legacy path, alias, no-move, and export-filename regression coverage
• apps/world-lab/src/components/world-lab.tsx: legacy browser-storage keys used only as migration inputs
• apps/world-lab/src/components/world-lab.test.tsx: legacy storage migration and malformed-value regression coverage

There are no remaining @agentborne/* package references or BlackSwampAI/agentborne source metadata references.

Validation

Repository-owner-confirmed local validation:

pnpm install --frozen-lockfile
pnpm validate
pnpm test:e2e
pnpm --filter @hexzero/experiment-archive test -- -t "imports an existing schema-v9 export with the legacy download filename"

All completed successfully. The Playwright run uses the deterministic scripted provider and makes no paid-provider request.

External rename

Do not merge automatically and do not rename the GitHub repository in this PR. After merge is explicitly confirmed, phase two will rename BlackSwampAI/agentborne to BlackSwampAI/hexzero and verify redirects, remotes, protections, issues/PRs, Actions, and external integrations.