You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ This builds the server at `tools/mcp-server/dist/src/index.js` and installs Node
80
80
> **Why some configs go in the workspace, others in your home directory:**
81
81
> VS Code-based clients (Claude Code, GitHub Copilot, Cline) are workspace-aware — they read config files from the repo root or `.vscode/`. Augment Code and Cursor are editor-level and read from your home directory (`~/.augment/`, `~/.cursor/`). This is why `wire-project` writes `.mcp.local.json` / `.vscode/mcp.json` into the project and merges `~/.augment/settings.json` / `~/.cursor/mcp.json` at the home level.
82
82
>
83
-
> **Fastest setup for any project:** run `~/bin/ai-ddtk/experimental/wire-project` — it auto-detects which editors are installed and writes the right config for each.
83
+
> **Fastest setup for any project:** run `~/bin/ai-ddtk/install.sh wire-project` — it auto-detects which editors are installed and writes the right config for each.
84
84
85
85
**GitHub Copilot / Cline / Continue (VS Code):**
86
86
-**Zero config** if the AI-DDTK VS Code extension is installed — it auto-registers the server via `mcpServerDefinitionProviders`
Copy file name to clipboardExpand all lines: CHANGELOG.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,25 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
16
16
## [2.1.1] - 2026-04-12
17
17
18
18
### Changed
19
+
-**`PROJECT/2-WORKING/CLEANUP.md`** — added an explicit evidence-based triage method for deciding doc/file lifecycle moves. The cleanup plan now treats `CHANGELOG.md`, `4X4.md`, and recent git commit history as primary signals when choosing between active, done, and misc states.
20
+
-**`PROJECT/2-WORKING/CLEANUP.md`** — added an operator preflight reminder near the start of the plan telling operators to make a commit or create a dedicated branch before starting cleanup work in a real repo.
21
+
-**`PROJECT/2-WORKING/CLEANUP.md`** — added a dedicated redaction-intake and naming-hygiene section so cleanup planning now explicitly covers client names, project names, and branded filenames, including an orchestrating-agent step to ask the user for protected terms before broad cleanup or publication passes.
22
+
-**`PROJECT/cleanup.sh` + `PROJECT/2-WORKING/CLEANUP.md`** — added a `scrub-intake` helper mode plus a reusable intake prompt template so orchestrating agents can ask the user for protected client names, project names, domains, and branded filenames before running scrub-related cleanup.
23
+
-**`PROJECT/cleanup.sh` + `PROJECT/2-WORKING/CLEANUP.md`** — added a `portable-doc` mode that regenerates `CLEANUP.md` with an embedded `cleanup.sh` appendix, so the plan can now travel as a one-file artifact while still keeping the executable script as the refresh source.
24
+
-**Cleanup naming + lifecycle pass** — renamed the active repo-organization plan to `PROJECT/2-WORKING/CLEANUP.md`, renamed the two repo cleanup scripts to `PROJECT/cleanup.sh` and `tools/cleanup.sh`, archived the Perplexity roadmap out of `2-WORKING`, and removed recreated inbox duplicates so current inbox/working states reflect actual active work.
25
+
-**Promoted `wire-project` and `post-flight`** — moved `experimental/wire-project` to `bin/wire-project`, added the supported `./install.sh wire-project` entrypoint, and moved `experimental/post-flight.sh` to `bin/post-flight` with MCP/runtime references updated to the new canonical paths.
26
+
-**`PROJECT/` lifecycle cleanup pass** — started Phase 3 repo cleanup by correcting overstated plan status, moving completed or reference-only project docs out of active inbox/working queues, and removing stale duplicate source copies that reappeared after lifecycle moves.
27
+
-**`tools/repo-hygiene.sh` + repo catalog artifacts** — expanded the repository catalog generator to emit the full Phase 2 schema (`file_type`, `owner_tool`, `canonical`, `generated`, `last_modified`, `status`, `tags`, `notes`), eliminated uncategorized lifecycle gaps, and added path-keyed manual overrides at `tools/repo-catalog.overrides.json`. The generated catalog remains at `tools/mcp-server/repo-catalog.json` and is now suitable as a real metadata layer for later cleanup and retrieval work.
28
+
-**`PROJECT/DOCS-INSTRUCTIONS.md` + `PROJECT/2-WORKING/P1-GET-ORGANIZED.md`** — aligned the organization docs with the actual repo state: marked only Phases 0–2 complete, fixed the working doc status, documented the repo catalog and overrides locations, and softened idealized temp/retention wording so legacy tracked files are treated as cleanup candidates rather than policy contradictions.
19
29
-**`tools/mcp-server/src/index.ts` + `src/registrations/*`** — MCP server registration is now split by domain so the entrypoint is composition-only and schemas live with the tools/resources they describe, reducing the maintenance cost of adding or changing MCP surface area.
20
30
-**External JSON contract hardening** — env probes, pw-auth JSON flows, Query Monitor profile retrieval, LocalWP JSON list parsing, and WPCC scan artifact loading now validate parsed JSON with Zod-backed schemas before returning data to MCP callers, turning silent shape drift into explicit contract errors.
21
31
-**Server registry source of truth** — moved the port registry backend from markdown parsing to canonical JSON at `tools/servers.registry.json`, with `tools/servers.md` generated from that data block so MCP reads/writes stop depending on markdown table formatting.
22
32
-**MCP test workflow** — normal unit tests and socket-binding tests are now separated into `test:unit`, `test:socket`, and `test:all`, so sandboxed environments can run the stable contract suite without failing on localhost/TCP or Unix-socket bind restrictions.
23
33
34
+
### Fixed
35
+
-**`bin/wire-project` gitignore append handling** — wiring a repo whose `.gitignore` did not end with a trailing newline could merge the new ignore entry into the previous line. The append flow now inserts a newline first when needed, so `.mcp.local.json` and similar entries are added safely in active repos.
36
+
-**`test/test-wire-project.sh`** — added a focused shell regression harness that creates a temp project with a newline-less `.gitignore`, runs `wire-project` twice under an isolated `HOME`, and asserts both safe append behavior and idempotence.
0 commit comments