Christian Gick b145e1effd feat(CF-338): Improve project detection to respect CF vs project scope ...

Problem: task-mcp treated all Infrastructure folders equally, causing framework/tooling work to be mis-scoped to random project codes instead of CF.

Solution:

1. Framework paths explicitly map to CF:

   - ClaudeFramework, AgilitonScripts, doco-cd, mcp-servers

   - deployment-system, monitoring-stack, backup-system

2. Infrastructure/* defaults to CF (framework work by default)

3. Project-specific infra services have explicit mappings:

   - caddy-gateway → CADDY

   - litellm → LLM

4. Apps/ still auto-detect project-specific codes (ST, GB, VPN, etc.)

This ensures:

- Framework tool changes → CF (correct scope)

- App features → Project codes (ST, GB, etc.)

- Infrastructure services → Own scope if needed

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-01-20 16:14:32 +02:00

..

tools

fix(CF-306): Validate session_id in memory_add to prevent FK violations

2026-01-20 10:17:53 +02:00

db.ts

feat(CF-338): Improve project detection to respect CF vs project scope

2026-01-20 16:14:32 +02:00

embeddings.ts

Fix CF-271: Add fallback text search to archive_search

2026-01-19 13:14:29 +02:00

index.ts

feat(CF-301): Implement task_move_project function

2026-01-20 08:05:34 +02:00

types.ts

feat(CF-166): Add investigation workflow with auto-linking

2026-01-19 19:15:25 +02:00