@tdk-landscape/tdk-cli-core 1.3.53 → 1.3.54

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/.openspec.yaml

@@ -1,2 +0,0 @@
-schema: spec-driven
-created: 2026-04-28

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/design.md

@@ -1,84 +0,0 @@
-## Context
-
-TDK CLI is a multi-language monorepo with TypeScript (CLI), Python (Discovery), and Starlark (Engine/Tilt configs). During initial exploration, several gaps were identified:
-
-**Current State:**
-- CLI `resource.ts` has 4 TODO comments for unimplemented features (database/cache checks, routes, worker logic, diff logic)
-- CLI `config.ts` has incomplete diff implementation
-- Test coverage exists but gaps likely in error handling paths
-- No systematic audit system for tracking technical debt
-
-**Constraints:**
-- Must not break existing functionality
-- Changes should be minimal and focused
-- All fixes must include tests where applicable
-- Must maintain compatibility with existing Tilt workflows
-
-## Goals / Non-Goals
-
-**Goals:**
-- Implement automated scanning to find TODO/FIXME/BUG/HACK markers across all languages
-- Fix high-priority TODOs in CLI commands (resource.ts, config.ts)
-- Add missing test coverage for critical error paths
-- Remove dead code and unused imports
-- Document all changes with clear commit messages
-
-**Non-Goals:**
-- Major refactoring or architecture changes
-- Adding new features beyond fixing existing TODOs
-- Rewriting working code without TODOs
-- Breaking changes to existing APIs
-
-## Decisions
-
-**Decision 1: Use grep-based scanning for initial audit**
-- **Rationale:** Simple, fast, works across all languages (TypeScript, Python, Starlark, Go)
-- **Alternative considered:** AST parsing - too complex for initial pass
-- **Implementation:** Shell script that searches for patterns: `TODO`, `FIXME`, `XXX`, `BUG`, `HACK`
-
-**Decision 2: Prioritize TODOs by file location and context**
-- **Rationale:** Not all TODOs are equal - CLI commands affect users directly
-- **Priority order:**
-  1. CLI user-facing commands (resource, config)
-  2. Core discovery logic
-  3. Engine utilities
-  4. Test infrastructure
-
-**Decision 3: Implement TODOs with minimal viable solutions**
-- **Rationale:** Don't over-engineer; match the scope implied by the TODO comment
-- **Example:** `// TODO: Add your routes here` → Add basic route placeholder, not full routing system
-
-**Decision 4: Add tests for all implemented TODOs**
-- **Rationale:** Ensures fixes work and don't regress
-- **Approach:** Unit tests for CLI, integration tests where appropriate
-
-## Risks / Trade-offs
-
-**Risk:** TODO comments may be intentionally vague and require product decisions
-- **Mitigation:** For ambiguous TODOs, implement minimal viable solution and document the limitation
-
-**Risk:** Implementing TODOs may introduce bugs in working code
-- **Mitigation:** All changes get tests; use existing test patterns from the codebase
-
-**Risk:** Dead code removal might break something that appears unused but is dynamically loaded
-- **Mitigation:** Only remove code after verifying no references exist (static analysis + runtime check)
-
-**Risk:** Test coverage gaps may be larger than initially estimated
-- **Mitigation:** Focus on critical paths first; document remaining gaps for future work
-
-## Migration Plan
-
-Not applicable - this is an internal maintenance change with no user-facing migration needed.
-
-Deployment steps:
-1. Run audit script to generate initial report
-2. Fix TODOs in priority order (CLI first)
-3. Add tests for all changes
-4. Run full test suite to ensure no regressions
-5. Submit as single PR or split by module (CLI, Discovery, Engine)
-
-## Open Questions
-
-1. Should we create a recurring audit job (CI) to catch new TODOs?
-2. What's the policy for TODOs that require product decisions vs. technical implementation?
-3. Should we establish a "no TODOs in main" policy after this cleanup?

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/proposal.md

@@ -1,31 +0,0 @@
-## Why
-
-The TDK CLI codebase has accumulated technical debt through TODO comments, incomplete implementations, and gaps in test coverage. These issues create friction for developers and risk bugs in production. Now is the right time to systematically scan the repository, identify gaps, and fix them before they compound into larger problems.
-
-## What Changes
-
-- **Scan entire codebase** for TODO/FIXME/BUG/HACK comments using automated detection
-- **Identify incomplete implementations** in CLI commands (resource, config with TODOs)
-- **Find missing test coverage** for critical paths in CLI and discovery modules  
-- **Fix high-priority issues**: Implement TODO items, add missing error handling, improve type safety
-- **Add missing documentation** for unclear or undocumented code paths
-- **Clean up technical debt**: Remove dead code, consolidate duplicates, fix linting issues
-
-## Capabilities
-
-### New Capabilities
-- `codebase-audit`: Automated scanning system for detecting technical debt markers (TODOs, missing tests, incomplete features)
-- `todo-resolution`: Implementation of high-priority TODO items in CLI commands
-- `test-gap-fill`: Adding missing test coverage for critical code paths
-- `dead-code-cleanup`: Identification and removal of unused code and imports
-
-### Modified Capabilities
-- None - this is a maintenance/polish change that doesn't modify existing specifications
-
-## Impact
-
-- **CLI**: TypeScript source files in `cli/src/` - implementing TODOs in resource.ts, config.ts
-- **Tests**: Python tests in `tests/tilt-engine/` and TypeScript tests in `cli/` - adding missing coverage
-- **Discovery**: Python modules in `discovery/` - improving error handling and edge cases
-- **Engine**: Starlark files in `engine/` - minor cleanups and documentation improvements
-- **No breaking changes**: All fixes are additive or internal improvements

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/specs/codebase-audit/spec.md

@@ -1,27 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Automated scanning detects technical debt markers
-The system SHALL provide automated scanning to detect TODO, FIXME, XXX, BUG, and HACK comments across all source files.
-
-#### Scenario: Scan TypeScript files
-- **WHEN** the audit script runs against the CLI source directory
-- **THEN** it SHALL output a list of all files containing TODO/FIXME/BUG/HACK markers with line numbers
-
-#### Scenario: Scan Python files
-- **WHEN** the audit script runs against the discovery directory
-- **THEN** it SHALL output a list of all files containing TODO/FIXME/BUG/HACK markers with line numbers
-
-#### Scenario: Scan Starlark files
-- **WHEN** the audit script runs against the engine directory
-- **THEN** it SHALL output a list of all files containing TODO/FIXME/BUG/HACK markers with line numbers
-
-### Requirement: Audit output is actionable
-The system SHALL generate an audit report that categorizes findings by priority and location.
-
-#### Scenario: Priority categorization
-- **WHEN** the audit completes
-- **THEN** findings SHALL be categorized as: CLI (user-facing), Core (discovery/engine), Test (infrastructure)
-
-#### Scenario: Report format
-- **WHEN** the audit generates a report
-- **THEN** it SHALL include file path, line number, marker type, and the TODO text for each finding

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/specs/dead-code-cleanup/spec.md

@@ -1,27 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Dead code is identified and removed
-The system SHALL identify and remove unused code, imports, and variables.
-
-#### Scenario: Unused imports removed
-- **WHEN** scanning TypeScript files in cli/src
-- **THEN** all unused imports SHALL be identified and removed
-
-#### Scenario: Unused functions removed
-- **WHEN** scanning Python files in discovery/
-- **THEN** functions with no references SHALL be flagged for review and removed if confirmed unused
-
-#### Scenario: Dead Starlark code removed
-- **WHEN** scanning Starlark files in engine/
-- **THEN** unused variables and functions SHALL be identified and removed
-
-### Requirement: Duplicate code is consolidated
-The system SHALL identify and consolidate duplicate code patterns where appropriate.
-
-#### Scenario: Duplicate templates consolidated
-- **WHEN** similar template patterns exist in multiple CLI commands
-- **THEN** they SHALL be consolidated into shared utility functions
-
-#### Scenario: Shared validation logic
-- **WHEN** validation logic is duplicated across modules
-- **THEN** it SHALL be moved to a shared validation utility

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/specs/test-gap-fill/spec.md

@@ -1,23 +0,0 @@
-## ADDED Requirements
-
-### Requirement: CLI commands have test coverage
-The system SHALL add missing test coverage for CLI command implementations.
-
-#### Scenario: Resource command tests
-- **WHEN** running the test suite
-- **THEN** resource.ts command SHALL have unit tests covering resource creation, template generation, and port assignment
-
-#### Scenario: Config command tests
-- **WHEN** running the test suite
-- **THEN** config.ts command SHALL have unit tests covering diff functionality and configuration loading
-
-### Requirement: Error handling paths are tested
-The system SHALL add tests for error handling and edge cases.
-
-#### Scenario: Invalid resource type handling
-- **WHEN** user specifies an invalid resource type
-- **THEN** the system SHALL throw an appropriate error and test SHALL verify this behavior
-
-#### Scenario: Missing manifest handling
-- **WHEN** discovering services with missing or invalid manifests
-- **THEN** the system SHALL handle gracefully and log appropriate warnings (tested)

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/specs/todo-resolution/spec.md

@@ -1,27 +0,0 @@
-## ADDED Requirements
-
-### Requirement: CLI resource command TODOs are implemented
-The system SHALL implement all TODO comments in cli/src/commands/resource.ts.
-
-#### Scenario: Resource database check TODO
-- **WHEN** creating a new resource with database dependencies
-- **THEN** the system SHALL check if the database exists and create it if missing
-
-#### Scenario: Resource cache check TODO
-- **WHEN** creating a new resource with cache dependencies
-- **THEN** the system SHALL check if the cache service is configured
-
-#### Scenario: Resource routes TODO
-- **WHEN** creating a new backend resource
-- **THEN** the system SHALL generate a basic route file template with health check endpoint
-
-#### Scenario: Resource worker logic TODO
-- **WHEN** creating a new worker resource
-- **THEN** the system SHALL generate a basic worker script template with job processing structure
-
-### Requirement: CLI config command diff is implemented
-The system SHALL implement the diff logic TODO in cli/src/commands/config.ts.
-
-#### Scenario: Config diff shows differences
-- **WHEN** user runs `tdk config diff`
-- **THEN** the system SHALL compare local and remote configuration and display differences

package/openspec/changes/archive/2026-04-29-scan-repo-gaps-fix/tasks.md

@@ -1,39 +0,0 @@
-## 1. Codebase Audit
-
-- [x] 1.1 Create audit script to scan for TODO/FIXME/BUG/HACK markers
-- [x] 1.2 Run audit against cli/src directory (TypeScript files)
-- [x] 1.3 Run audit against discovery/ directory (Python and Starlark files)
-- [x] 1.4 Run audit against engine/ directory (Starlark files)
-- [x] 1.5 Generate prioritized report with CLI, Core, and Test categories
-
-## 2. CLI TODO Resolution
-
-- [x] 2.1 Implement database check TODO in cli/src/commands/resource.ts
-- [x] 2.2 Implement cache check TODO in cli/src/commands/resource.ts
-- [x] 2.3 Implement routes TODO (generate route file template) in resource.ts
-- [x] 2.4 Implement worker logic TODO (generate worker template) in resource.ts
-- [x] 2.5 Implement diff logic TODO in cli/src/commands/config.ts
-
-## 3. Test Coverage Improvements
-
-- [x] 3.1 Add unit tests for resource.ts command (creation, templates, port assignment)
-- [x] 3.2 Add unit tests for config.ts command (diff functionality)
-- [x] 3.3 Add error handling tests for invalid resource types
-- [x] 3.4 Add tests for missing/invalid manifest handling in discovery
-- [x] 3.5 Run full test suite and fix any regressions
-
-## 4. Dead Code Cleanup
-
-- [x] 4.1 Identify and remove unused imports in cli/src TypeScript files
-- [x] 4.2 Identify and flag unused functions in discovery/ Python files
-- [x] 4.3 Identify and flag unused variables/functions in engine/ Starlark files
-- [x] 4.4 Consolidate duplicate template patterns in CLI commands
-- [x] 4.5 Move duplicated validation logic to shared utilities
-
-## 5. Documentation and Finalization
-
-- [x] 5.1 Document all changes in commit messages
-- [x] 5.2 Update AGENTS.md files if implementation patterns changed
-- [x] 5.3 Run final linting and type checking
-- [x] 5.4 Verify all tests pass
-- [x] 5.5 Archive the audit report for future reference

package/openspec/changes/archive/2026-06-25-landscape-consolidation/.openspec.yaml

@@ -1,2 +0,0 @@
-schema: spec-driven
-created: 2026-06-25

package/openspec/changes/archive/2026-06-25-landscape-consolidation/design.md

@@ -1,80 +0,0 @@
-## Context
-
-### CLI Duplication
-`beauty-crm/cli/` and `tdk-cli/cli/` both contain the `@tdk-landscape/tdk-cli-core` package. The `beauty-crm/cli/package.json` declares `"repository.directory": "cli"` pointing to `tdk-landscape/tdk-cli`, confirming it was originally published from the tdk-cli monorepo workspace. Over time, `tdk-cli/cli/` has evolved (12 src files, generator support, DRY assessment) while `beauty-crm/cli/` has lagged behind (9 src files). Any developer fixing the CLI must choose which copy to edit — and usually picks the wrong one.
-
-### AI Config Sprawl
-The beauty-crm monorepo has accumulated configs for every AI coding assistant that gained popularity:
-
-| Assistant | Type | Size |
-|-----------|------|------|
-| `.claude/` | Dir | skills, CLAUDE.md (757 lines) |
-| `.cursor/` | Dir | rules, mcp.json, Dockerfile |
-| `.continue/` | Dir | skills config |
-| `.roo/` | Dir | 7 rulesets, mcp.json |
-| `.serena/` | Dir | memories, prompt templates |
-| `.agents/` | Dir | skills, mempalace |
-| `.augment/` | Dir | agents, skills |
-| `.kiro/` | Dir | agents, skills, settings, specs |
-| `CLAUDE.md` | File | 757 lines (canonical project context) |
-| `.cursorrules` | File | 32 lines (duplicates CLAUDE.md) |
-| `.windsurfrules` | File | 2855 lines (duplicates CLAUDE.md + more) |
-| `.roomodes` | File | 47 lines (mode definitions) |
-| `.augment-guidelines` | File | 457 lines (duplicates CLAUDE.md) |
-
-Most contain overlapping project context (tech stack, architecture, conventions) which creates a maintenance tax — every time the tech stack or conventions change, 13+ files need updating. The `.cursorrules` is a 32-line subset of `CLAUDE.md`. The `.windsurfrules` is 2855 lines that includes the full `CLAUDE.md` content plus extra.
-
-## Goals / Non-Goals
-
-**Goals:**
-- Remove `beauty-crm/cli/` and replace with a symlink to `tdk-cli/cli/`
-- Update any beauty-crm tooling that references `beauty-crm/cli/` directly
-- Consolidate all AI configs into one canonical location per project
-- Remove duplicate root-level config files (`.cursorrules`, `.windsurfrules`, `.roomodes`, `.augment-guidelines`)
-- Move `.cursor/mcp.json`, `.roo/` mode definitions into a shared format if they add unique value
-- Verify no CI/CD breakage
-
-**Non-Goals:**
-- Merging AI assistant-specific features (e.g., Serena memories, Roo rulesets) — keep them in `.claude/skills/` or let each assistant read its own format
-- Renaming the entire root directory structure
-- Changing how `tdk-cli/` is organized internally
-- Adding or removing any AI assistant support — only consolidating configs
-
-## Decisions
-
-### Decision 1: Remove Completely (No Symlink)
-**Path**: `git rm -r beauty-crm/cli/` — deleted from git and disk, no replacement.
-**Rationale**: A symlink breaks `git add pathspec` resolution (git treats symlinked directories as single blobs and cannot traverse them). Since no scripts, workspaces, or CI pipelines reference `beauty-crm/cli/`, there's nothing to break. Removing entirely is the cleanest solution.
-**Alternatives considered**:
-- Symlink to `../tdk-cli/cli/` — Rejected: breaks `git add` and other git operations
-- Keep as-is (do nothing) — Drift will continue to grow
-
-### Decision 2: Canonical AI Config = `.claude/` + `CLAUDE.md`
-**Rationale**: `CLAUDE.md` is the most comprehensive single file (757 lines covering tech stack, architecture, conventions). `.claude/` is the directory format used by Claude Code and Opencode. Other assistants (Cursor, Windsurf, Continue, Roo, Serena) can read symlinked or imported copies.
-**Implementation**: Other root config files get removed. Each assistant's directory gets a README pointing to `CLAUDE.md` as canonical.
-
-### Decision 3: Preserve `.cursor/mcp.json` as Shared MCP Config
-**Rationale**: MCP server configuration is tool-agnostic and useful across assistants. Move it to a shared location or keep as a thin reference.
-**Approach**: Keep `.cursor/mcp.json` but add a comment header pointing to `CLAUDE.md` for context. Alternatively, move to `.opencode/mcp.json` if opencode is the canonical tool.
-
-### Decision 4: Keep `.roo/` Rulesets
-**Rationale**: Roo's role-based rulesets (architect, code, debug, etc.) are unique to Roo's multi-agent workflow and don't duplicate CLAUDE.md content. They add value.
-**Approach**: Leave `.roo/rules/` in place. Only remove root-level `.roomodes` if Roo can find its modes via the directory.
-
-### Decision 5: No Cross-Project AI Config Sync
-**Rationale**: `identity/`, `platform/`, and `tdk-cli/` don't have AI configs. Adding them would be scope creep. Each project should opt in when ready.
-**Approach**: Document in CONTRIBUTING.md that each project manages its own AI configs, and `.claude/` + `CLAUDE.md` is the recommended canonical format.
-
-## Risks / Trade-offs
-
-**Risk**: Symlink breaks in CI/CD (Docker, git checkout without submodules)
-- **Mitigation**: Symlinks work with `git clone` and Docker COPY. Test explicitly.
-
-**Risk**: Developer has `.cursorrules` or `.windsurfrules` open in muscle memory and is confused when gone
-- **Mitigation**: Leave a one-line comment file: `.cursorrules → see CLAUDE.md`
-
-**Risk**: Cursor/Continue/Roo stop working optimally without their config files
-- **Mitigation**: Each assistant can still use its own directory format. We only remove root-level _files_ that duplicate `CLAUDE.md`. The directories (`.cursor/`, `.continue/`, `.roo/`) stay but get trimmed.
-
-**Risk**: Some AI assistant relies on `.windsurfrules` being 2855 lines (it contains everything)
-- **Mitigation**: WindSurf can also read `CLAUDE.md` directly. The `CLAUDE.md` is already comprehensive.

package/openspec/changes/archive/2026-06-25-landscape-consolidation/proposal.md

@@ -1,40 +0,0 @@
-## Why
-
-The TDK landscape has accumulated two inefficiencies from its extraction from the original `beauty-crm` monorepo:
-
-1. **Duplicated CLI client**: `beauty-crm/cli/` is a vendored copy of `tdk-cli/cli/` (both publish as `@tdk-landscape/tdk-cli-core`). This means every CLI fix must be applied twice, and the two copies have already diverged — `beauty-crm/cli/` has 9 source files while `tdk-cli/cli/` has 12 with additional features. This will only worsen over time.
-
-2. **AI config sprawl**: `beauty-crm/` contains configuration for 8 AI coding assistants (`.claude/`, `.cursor/`, `.continue/`, `.roo/`, `.serena/`, `.agents/`, `.augment/`, `.kiro/`) plus 5 root-level config files (`CLAUDE.md`, `.cursorrules`, `.windsurfrules`, `.roomodes`, `.augment-guidelines`). Most contain duplicate project context. Developers waste time maintaining 13+ config files that say the same thing.
-
-Fixing both reduces maintenance burden, clarifies the canonical source of truth, and prevents future drift.
-
-## What Changes
-
-### Workstream A: CLI Duplicate Removal
-- Remove `beauty-crm/cli/` entirely via `git rm`
-- No symlink — symlinks break `git add` pathspec resolution
-- Update any `beauty-crm/` scripts/build pipelines that reference the old path
-
-### Workstream B: AI Config Consolidation
-- Choose one canonical AI assistant config per project (recommend: `.claude/` + `CLAUDE.md`)
-- Remove duplicated root config files (`.cursorrules`, `.windsurfrules`, `.roomodes`, `.augment-guidelines`)
-- Consolidate `beauty-crm/.kiro/`, `beauty-crm/.agents/`, `beauty-crm/.augment/` into `beauty-crm/.claude/` or a shared `.ai-tools/` directory
-- Add `.cursor/mcp.json` as a workspace-level config (not project-specific)
-- Document which AI config is canonical for each project
-
-## Capabilities
-
-### New Capabilities
-- `cli-source-consolidation`: Single source of truth for `@tdk-landscape/tdk-cli-core`
-- `ai-config-consolidation`: Unified AI assistant configuration
-
-### Modified Capabilities
-- Existing specs in `tdk-cli/openspec/specs/` may need minor updates if they reference `beauty-crm/cli/`
-
-## Impact
-
-- **Files removed**: beauty-crm/cli/ (~50 files), AI root configs (5 files), AI assistant dirs (5+ dirs)
-- **Files added**: 1 symlink, 1-2 consolidated config files
-- **Dependencies**: CI/CD pipelines that reference beauty-crm/cli/ need updating
-- **Breaking Changes**: Any tooling that directly references `beauty-crm/cli/bin/tdk.js` will need to use `tdk-cli/cli/bin/tdk.js`
-- **Risk Level**: Low-Medium. CLI removal is mechanical and testable. AI config changes are cosmetic but need care not to break developer workflows.

package/openspec/changes/archive/2026-06-25-landscape-consolidation/spec.md

@@ -1,52 +0,0 @@
-# landscape-consolidation Specification
-
-## Purpose
-
-The TDK landscape has two sources of maintenance waste: a vendored duplicate of the `@tdk-landscape/tdk-cli-core` package in `beauty-crm/cli/` that has diverged from the canonical `tdk-cli/cli/`, and 13+ AI assistant config entries in `beauty-crm/` with overlapping project context spread across 8 directories and 5 root files. Consolidating both reduces maintenance burden and establishes canonical sources of truth.
-
-## Requirements
-
-### Requirement: Single CLI source of truth
-
-All source code and tooling for the `@tdk-landscape/tdk-cli-core` package SHALL originate from `tdk-cli/cli/`. The `beauty-crm/cli/` directory SHALL NOT contain its own copy of CLI source.
-
-#### Scenario: Remove duplicate CLI directory
-- **WHEN** inspecting the `beauty-crm/` project root
-- **THEN** there SHALL be no `cli/` directory containing standalone `@tdk-landscape/tdk-cli-core` source
-
-#### Scenario: Directory removed completely (no symlink)
-- **WHEN** inspecting the `beauty-crm/` project root
-- **THEN** `beauty-crm/cli/` SHALL NOT exist as a directory or symlink
-
-#### Scenario: No broken references after removal
-- **WHEN** searching `beauty-crm/` for direct `beauty-crm/cli/` path references
-- **THEN** no such references SHALL exist in scripts, configs, or documentation
-
-### Requirement: Canonical AI project context
-
-All AI assistants operating in `beauty-crm/` SHALL use `CLAUDE.md` as the single canonical source for project context (tech stack, architecture, conventions).
-
-#### Scenario: Remove redundant root-level config files
-- **WHEN** listing root-level config files in `beauty-crm/`
-- **THEN** `.cursorrules`, `.windsurfrules`, and `.augment-guidelines` SHALL NOT exist
-
-#### Scenario: Assistant directory structure preserved
-- **WHEN** an AI assistant reads its configuration
-- **THEN** its native directory SHALL still exist (`.cursor/`, `.continue/`, `.roo/`, `.serena/`, `.agents/`, `.augment/`, `.kiro/`)
-- **AND** SHALL NOT have been moved or reformatted
-
-#### Scenario: Cross-reference from assistant configs
-- **WHEN** an AI assistant initializes
-- **THEN** its config files SHALL contain a comment or README referencing `CLAUDE.md` for project context
-
-### Requirement: No regression in CLI functionality
-
-Removing `beauty-crm/cli/` SHALL NOT break any existing functionality that depends on the `@tdk-landscape/tdk-cli-core` package.
-
-#### Scenario: No workspace resolution errors after removal
-- **WHEN** running `bun install` in `beauty-crm/`
-- **THEN** it SHALL NOT error due to the removed `cli/` directory
-
-#### Scenario: No workspace resolution errors
-- **WHEN** running `bun install` in `beauty-crm/`
-- **THEN** it SHALL NOT error due to the removed `cli/` directory

package/openspec/changes/archive/2026-06-25-landscape-consolidation/tasks.md

@@ -1,51 +0,0 @@
-## 1. CLI Duplicate — Audit & Verify
-
-- [x] 1.1 Confirm `beauty-crm/cli/` is not listed in `beauty-crm/package.json` workspaces
-- [x] 1.2 Confirm no CI/CD or scripts reference `beauty-crm/cli/` as a build path
-- [x] 1.3 Verify `beauty-crm/cli/package.json` name is `@tdk-landscape/tdk-cli-core` (not `@beauty-crm/cli`)
-- [x] 1.4 Verify `tdk-cli/cli/` has superset of files vs `beauty-crm/cli/` (72 vs 26 source files)
-- [x] 1.5 Check `beauty-crm/bun.lock` does NOT lock `@tdk-landscape/tdk-cli-core` to a `file:cli` path
-- [x] 1.6 Check `.tilt-engine/` and `Tiltfile` for any references to `beauty-crm/cli/`
-
-## 2. CLI Duplicate — Remove
-
-- [x] 2.1 `git rm -r beauty-crm/cli/` (removed from git and disk)
-- [x] 2.2 Verify no stale references: `rg` found zero references
-
-## 3. AI Config — Audit Current State
-
-- [x] 3.1 Catalog all AI assistant configs in `beauty-crm/`:
-  - Directories: `.claude/`, `.cursor/`, `.continue/`, `.roo/`, `.serena/`, `.agents/`, `.augment/`, `.kiro/`
-  - Root files: `CLAUDE.md`, `.cursorrules`, `.windsurfrules`, `.roomodes`, `.augment-guidelines`
-- [x] 3.2 Identify content overlap:
-  - `.cursorrules` — 32-line communication style (no project context)
-  - `.windsurfrules` — 2855-line superset of CLAUDE.md
-  - `.augment-guidelines` — 457-line partially overlapping
-- [x] 3.3 Check `.roo/rules/` — unique workflow instructions (dev_workflow, self_improve, taskmaster)
-- [x] 3.4 Check `.cursor/mcp.json` — unique MCP server configs (task-master-ai, tilt)
-
-## 4. AI Config — Consolidate
-
-- [x] 4.1 Remove `.cursorrules` (redundant with `CLAUDE.md`)
-- [x] 4.2 Remove `.windsurfrules` (redundant with `CLAUDE.md`)
-- [x] 4.3 Remove `.augment-guidelines` (redundant with `CLAUDE.md`)
-- [x] 4.4 Keep `.roomodes` (defines Roo's custom mode slugs — not redundant with CLAUDE.md)
-- [x] 4.5 Keep all AI assistant directories in place (each reads from its own native path):
-  - `.cursor/`, `.continue/`, `.roo/`, `.serena/`, `.agents/`, `.augment/`, `.kiro/`
-- [x] 4.6 Add comment/README to each assistant config pointing to `CLAUDE.md`:
-  - `.cursor/mcp.json` → `_comment` field
-  - `.roo/README.md`, `.serena/README.md`, `.agents/README.md`, `.augment/README.md`, `.kiro/README.md`, `.continue/README.md`
-
-## 5. AI Config — Documentation
-
-- [x] 5.1 Add banner to `CLAUDE.md` declaring it canonical source of truth
-- [x] 5.2 Keep `.cursor/rules/` in place (native Cursor format)
-- [x] 5.3 Verify `identity/`, `platform/`, `tdk-cli/` don't need AI configs (scope boundary)
-
-## 6. Verification
-
-- [x] 6.1 Run `git status` — clean, 44 files changed
-- [x] 6.2 N/A (no symlink — removed directly via `git rm`)
-- [x] 6.3 No broken references found
-- [x] 6.4 CLAUDE.md is valid markdown, loadable by any AI
-- [ ] 6.5 Ask team to test their preferred AI assistant still works after consolidation

package/openspec/changes/archive/2026-09-17-fix-generated-stack-boot/.openspec.yaml

@@ -1,2 +0,0 @@
-schema: spec-driven
-created: 2026-09-17

package/openspec/changes/archive/2026-09-17-fix-generated-stack-boot/design.md

@@ -1,43 +0,0 @@
-# Fix Generated Stack Boot - Design
-
-## Context
-
-`tdk project` and `tdk resource` produce output that must run on a fresh machine with Docker + Tilt. Two defects broke this path for every user: (1) the backend source template emitted a literal newline inside a single-quoted `console.log` string, making every generated service uncompilable; (2) the generated Tiltfile pointed at an author-specific absolute path (`/private/var/www/2025/ollamar1/tdk-cli`) and fell back to a private GitHub repo that cannot be cloned, causing `tdk up` to hang in a git retry loop. The fixes below were implemented and verified in an isolated container (fixed binary rebuilt from source, `bun run` + `curl /health` green, `tilt ci` loads the vendored extension and reports a healthy workspace).
-
-## Goals / Non-Goals
-
-**Goals:**
-- Generated services compile and serve `/health` on first run.
-- `tdk up` loads its Tiltfile on any machine with zero network or private-repo dependency.
-- Generated output contains no machine-specific paths and fails fast with actionable errors when misconfigured.
-- Extension loading uses a truthful local probe.
-
-**Non-Goals:**
-- Rewriting the TDK Tilt extension itself or its orchestration semantics.
-- Making the private `tdk-cli` source repo public.
-- Changing the generated `service.json` manifest shape (tracked separately in manifest-field-migration).
-- Container-to-host DNS routing (traefik `*.beauty-crm.localhost` mapping) is outside this change.
-
-## Decisions
-
-### D1. Do not hardcode or publish; vendor instead
-Vendor the extension into each generated project (`.tdk/.tdk-out/tdk-cli-ext/`) at generation time. Rationale: matches the "releases public, source private" position, works offline, and a vendored project stays reviewable and relocatable. The source is located via, in order: `$TDK_EXTENSION_SOURCE`, an executable-adjacent `tdk-cli` checkout, then a `../tdk-cli` sibling of the project root. Missing source logs a warning; the Tiltfile then fails fast with recovery instructions.
-
-### D2. Escape newlines at the template boundary
-In `cli/src/commands/resource.ts`, `getBackendIndexTemplate` emits `console.log('\n🚀 ...')`. The template is a JS template literal, so `\n` becomes a real newline in the emitted file. The source therefore uses `\\n` so generated files contain the two-character escape sequence and remain valid Bun source.
-
-### D3. Fail fast instead of a private-repo fallback
-The Tiltfile resolution order is: vendored path -> `$TDK_EXTENSION_PATH` -> `fail(...)` with the three recovery options. This eliminates the infinite `git clone` retry against `github.com/tdk-landscape/tdk-cli` (private, 404 to unauthenticated clients).
-
-### D4. Truthful local probe
-The presence probe must produce output: `test -d <path> && echo yes || echo no`. A probe returning `""` (as the first iteration did) silently disables detection and routes every run to the fail-fast branch.
-
-### D5. Vendoring lives in `generateMasterConfigs`
-The copy step runs in `generateMasterConfigs` (alongside writing `Tiltfile`, `spec.master`, etc.) so regeneration repairs a stale or missing vendored extension.
-
-## Risks / Trade-offs
-
-- **Project size**: vendoring adds ~2.5 MB of starlark per project. Accepted for offline, private-repo-free bootstrapping; the copied set is limited to `Tiltfile`, `engine/`, `discovery/`, `specs/`, `ext/`.
-- **Stale binary releases**: released `release-dist-*` binaries still contain both bugs. Release artifacts must be rebuilt (proven command: `bun build --compile --target=bun-linux-arm64 --outfile tdk-linux-arm64 cli/src/cli.ts`) and republished before users see the fix.
-- **Probe coupling**: detection depends on `local()` emitting the echo; documented in the template comment so future edits keep the `&& echo yes || echo no` tail.
-- **Sandbox verification ceiling**: full container orchestration (image builds via traefik network, `*.beauty-crm.localhost` DNS) requires a host network; the isolated-container verification covers generation, compilation, Tiltfile loading, service discovery, resource creation, and workspace health.

package/openspec/changes/archive/2026-09-17-fix-generated-stack-boot/proposal.md

@@ -1,29 +0,0 @@
-## Why
-
-Generated projects from `tdk project` and `tdk resource` shipped two blockers that broke the quickstart for every user: generated Bun services did not compile (the backend template emits a literal newline inside a `console.log('...')` string, producing `Unterminated string literal`), and `tdk up` could never load its Tiltfile because it hardcoded a machine-specific extension path and fell back to a private GitHub repo that triggers an endless git-clone retry loop. Both were reproduced in an isolated Docker container and verified fixed in source, but the fixes are not yet reflected in released binaries or a tracked spec.
-
-## What Changes
-
-- `cli/src/commands/resource.ts`: escape newlines in the generated backend `src/index.ts` so emitted files contain `\n` and compile (`console.log('\n...')`).
-- `cli/templates/Tiltfile.hbs`: resolve the TDK Tilt extension in order - vendored in-project copy (`.tdk/.tdk-out/tdk-cli-ext`) -> `$TDK_EXTENSION_PATH` -> fail fast with actionable instructions. Remove the hardcoded `/private/var/www/2025/ollamar1/tdk-cli` path and the private-repo fallback.
-- `cli/src/generator/template-engine.ts`: vendor the extension (engine/discovery/specs/ext) into `.tdk/.tdk-out/tdk-cli-ext/` during `generateMasterConfigs`, so `tdk up` works offline on any machine without GitHub access. Source is auto-detected via `$TDK_EXTENSION_SOURCE`, executable-adjacent checkout, or a `../tdk-cli` sibling.
-- `cli/templates/Tiltfile.hbs`: fix the local-directory probe to echo its result (`test -d <path> && echo yes || echo no`); the previous probe returned `""`, so the vendored extension was never detected and `tdk up` always failed at the new fail-fast gate.
-- Rebuild release binaries from the fixed source and republish to `tdk-landscape/tdk-cli-releases` (**BREAKING** for existing releases - new generated output shape).
-
-## Capabilities
-
-### New Capabilities
-
-- `self-contained-generated-projects`: generated projects must boot without network or private-repo access - extension vendored at generation time, Tiltfile loads it from a local `file://` repo, and generated service sources compile on first `bun run`.
-
-### Modified Capabilities
-
-- `manifest-field-migration`: no requirement changes; generated `service.json` shape is unchanged.
-
-## Impact
-
-- `cli/src/commands/resource.ts` - backend index template escaping.
-- `cli/templates/Tiltfile.hbs` - extension resolution and probe.
-- `cli/src/generator/template-engine.ts` - vendoring step, `.tdk/.tdk-out/tdk-cli-ext/` output.
-- `release-dist-*` snapshots - must be regenerated from fixed source.
-- Verification: generated services compile and serve `/health` via Bun; `tilt ci` on a generated Tiltfile loads the vendored extension, discovers services, creates resources, and reports a healthy workspace.