feat: Rename application from "Codewalk District" to "Codewalkers"

Update all user-facing strings (HTML title, manifest, header logo,
browser title updater), code comments, and documentation references.
Folder name retained as-is.
This commit is contained in:
Lukas May
2026-03-05 12:05:08 +01:00
parent 427f93e136
commit 0ff65b0b02
33 changed files with 46 additions and 48 deletions

View File

@@ -1,4 +1,4 @@
# Project Milestones: Codewalk District
# Project Milestones: Codewalkers
## v1.3 Parallel Execution & UI Design (Shipped: 2026-02-02)

View File

@@ -1,4 +1,4 @@
# Codewalk District
# Codewalkers
## What This Is

View File

@@ -1,4 +1,4 @@
# Requirements: Codewalk District
# Requirements: Codewalkers
**Defined:** 2026-01-30
**Core Value:** Coordinate multiple Claude Code agents without losing track or stepping on each other.

View File

@@ -1,4 +1,4 @@
# Roadmap: Codewalk District
# Roadmap: Codewalkers
## Overview

View File

@@ -44,7 +44,7 @@ Output: A working `packages/web/` directory with Vite dev server, Tailwind CSS,
- `packages/web/tsconfig.app.json` targeting ES2020, module ESNext, moduleResolution bundler, strict mode, jsx react-jsx, include `src`.
- `packages/web/index.html` standard Vite entry pointing to `/src/main.tsx`.
- `packages/web/src/main.tsx` rendering `<App />` into `#root`.
- `packages/web/src/App.tsx` minimal component returning `<div>Codewalk District</div>`.
- `packages/web/src/App.tsx` minimal component returning `<div>Codewalkers</div>`.
3. Update root `package.json`:
- Add `"workspaces": ["packages/*"]` for npm workspaces.
@@ -118,7 +118,7 @@ npm run dev:web starts dev server (verify it starts, then kill).
- `@/` → `./src/` (standard shadcn convention)
- Install `@types/node` as dev dependency for path resolution in vite config.
7. Update `packages/web/src/App.tsx` to use a Tailwind class (e.g., `<div className="text-2xl font-bold p-8">Codewalk District</div>`) to verify Tailwind works.
7. Update `packages/web/src/App.tsx` to use a Tailwind class (e.g., `<div className="text-2xl font-bold p-8">Codewalkers</div>`) to verify Tailwind works.
8. Run `npm install` from root after adding dependencies.
</action>

View File

@@ -11,7 +11,7 @@ autonomous: true
<objective>
Wire tRPC React Query client to connect the frontend to the existing backend server.
Purpose: Enable type-safe data fetching from the Codewalk District backend. All subsequent UI screens (dashboard, detail, inbox) will use these tRPC hooks for data.
Purpose: Enable type-safe data fetching from the Codewalkers backend. All subsequent UI screens (dashboard, detail, inbox) will use these tRPC hooks for data.
Output: Working tRPC client with React Query provider, connected to backend via Vite dev proxy.
</objective>
@@ -126,7 +126,7 @@ Output: Working tRPC client with React Query provider, connected to backend via
return (
<div className="p-8">
<h1 className="text-2xl font-bold">Codewalk District</h1>
<h1 className="text-2xl font-bold">Codewalkers</h1>
<p className="text-muted-foreground mt-2">
Server: {health.data?.status ?? 'connecting...'}
</p>

View File

@@ -194,7 +194,7 @@ Component files exist in packages/web/src/components/ui/.
Initiatives Agents Tasks Settings
```
Implementation:
- Header with app title "Codewalk District" on the left
- Header with app title "Codewalkers" on the left
- "New Initiative" button on the right (placeholder handler for now)
- Navigation tabs: Initiatives (links to /initiatives), Inbox (links to /inbox)
- Skip "Agents", "Tasks", "Settings" tabs for now — not in Phase 16-19 scope. Include them as disabled/greyed out.

View File

@@ -58,7 +58,7 @@ All three commands succeed with zero errors.
1. Start backend: `cw --server` (or however the server starts)
2. Start frontend: `npm run dev:web`
3. Visit: http://localhost:5173 (Vite default port)
4. Verify: Navigation header shows "Codewalk District" with nav tabs
4. Verify: Navigation header shows "Codewalkers" with nav tabs
5. Click "Initiatives" tab → should show dashboard stub
6. Click "Inbox" tab → should show inbox stub
7. Verify: Tailwind styling renders (text should be styled, not raw HTML)

View File

@@ -9,7 +9,7 @@
## System Overview
```
Codewalk District Architecture
Codewalkers Architecture
================================================================================
+------------------+
@@ -1044,7 +1044,7 @@ const container = createContainer();
program
.name('cw')
.description('Codewalk District - Multi-agent workspace orchestrator')
.description('Codewalkers - Multi-agent workspace orchestrator')
.version('0.1.0');
program

View File

@@ -1,4 +1,4 @@
# Feature Research: Codewalk District
# Feature Research: Codewalkers
## Metadata
- **Domain**: Multi-agent orchestration / Developer tooling

View File

@@ -1,4 +1,4 @@
# Codewalk District: Critical Pitfalls Reference
# Codewalkers: Critical Pitfalls Reference
- **Domain:** Multi-agent orchestration / Developer tooling
- **Researched:** 2026-01-30

View File

@@ -149,7 +149,7 @@ const program = new Command();
program
.name('cw')
.description('Codewalk District - Multi-agent orchestration')
.description('Codewalkers - Multi-agent orchestration')
.version('0.1.0');
program

View File

@@ -1,13 +1,13 @@
# Project Research Summary
**Project:** Codewalk District
**Project:** Codewalkers
**Domain:** Multi-agent orchestration / Developer tooling
**Researched:** 2026-01-30
**Confidence:** HIGH
## Executive Summary
Codewalk District enters a space where the basic problem (running multiple Claude Code agents in parallel) is already solved by tools like Claude Squad, par, and Claude Flow. The differentiation opportunity isn't in parallel execution—that's table stakes now. The gap is in **coordination quality**: preventing conflicts before they happen, making review manageable, and keeping the developer in control without drowning in context switches.
Codewalkers enters a space where the basic problem (running multiple Claude Code agents in parallel) is already solved by tools like Claude Squad, par, and Claude Flow. The differentiation opportunity isn't in parallel execution—that's table stakes now. The gap is in **coordination quality**: preventing conflicts before they happen, making review manageable, and keeping the developer in control without drowning in context switches.
The recommended approach is a TypeScript CLI with embedded tRPC server, SQLite persistence, and hexagonal architecture. Skip Redis/BullMQ—SQLite with WAL mode handles 10-15k tasks/second locally. Use Commander.js (not oclif), Drizzle ORM with better-sqlite3, and execa for process spawning. The modular monolith structure with clear port/adapter boundaries sets up future evolution without rewrites.