Relocates ModuleOrchestrator, ServiceCollectionExtensions, and ApiPrefixConvention from SlpModularCms.Api into SlpModularCms.Core.Hosting so a new Master-less SlpModularCms.Api.Slave host project (ports 5285/7222) can share the same bootstrap code without duplicating it. This lets a developer run a master instance and a slave instance side by side locally to test the master/slave connection, without touching the existing master/slave protocol itself. Relocates the two orchestrator/convention test files from Modules.Identity.Tests to Core.Tests, dropping an incidental ProjectReference to SlpModularCms.Api that existed only for those tests. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
AI-DLC State Tracking
Project Information
- Feature Name: Local Dev Master/Slave Setup
- Feature Slug: local-dev-master-slave-setup
- Project Type: Brownfield
- Start Date: 2026-07-02T00:00:00Z
- Current Stage: CONSTRUCTION - Unit 2 (Frontend dual-instance tooling & runbook) - Code Generation
- Branch: unknown
Workspace State
- Existing Code: Yes
- Reverse Engineering Needed: No (artifacts exist in
aidlc-docs/_shared/reverse-engineering/) - Workspace Root: K:\Development\Projects\SlpModularCms
Code Location Rules
- Application Code: Workspace root (NEVER in aidlc-docs/)
- Feature Documentation: aidlc-docs/features/local-dev-master-slave-setup/ only
- Shared Artifacts: aidlc-docs/_shared/
Language Configuration
- Documentation Language: English
- Conversation Language: Dutch (User Language)
Extension Configuration
[Will be populated during Requirements Analysis]
Execution Plan Summary
- Total Stages: Workspace Detection, Requirements Analysis, User Stories (skipped), Workflow Planning, Application Design, Units Generation, Code Generation (x2 units), Build and Test
- Stages to Execute: Workflow Planning, Application Design, Units Generation, Code Generation (Unit 1: Backend dual-instance hosting; Unit 2: Frontend dual-instance tooling & runbook), Build and Test
- Stages to Skip: User Stories (dev tooling, no user-facing change); Functional Design, NFR Requirements, NFR Design, Infrastructure Design (all per-unit — no new business logic, NFRs already fully captured in requirements.md, no infrastructure/cloud involved)
Stage Progress
🔵 INCEPTION PHASE
- Workspace Detection — Complete
- Requirements Analysis — Complete (
inception/requirements/requirements.md) - User Stories — Skipped (dev tooling, no user-facing functional change)
- Workflow Planning — Complete (
inception/plans/execution-plan.md) - Application Design — Complete (
inception/application-design/) - Units Generation — Complete (
inception/application-design/unit-of-work*.md)
🟢 CONSTRUCTION PHASE
- Unit 1 (Backend dual-instance hosting) — Code Generation complete (
construction/unit-1-backend-dual-instance-hosting/code/summary.md); build + full test suite verified green; manual module-discovery check confirms slave excludes Master - Unit 2 (Frontend dual-instance tooling & runbook) — In Progress
- Build and Test — Not started