Legendary: Specification Alignment — Close All Gaps Between Implementation and Specification #945

New issue

Open

opened 2026-03-14 03:15:20 +00:00 by freemo · 0 comments

freemo commented

2026-03-14 03:15:20 +00:00

Owner

Background

A systematic audit of the codebase against docs/specification.md revealed multiple areas where the implementation diverges from the specification. The specification is the authoritative source of truth (per CONTRIBUTING.md §Specification-First Development), and all discrepancies must be resolved by aligning the code to the spec.

This Legendary groups all Epics whose primary purpose is closing a verified gap between the current implementation and the specification. It spans multiple milestones (v3.4.0 through v3.8.0+) and covers protocol compliance, language intelligence, context assembly, output rendering, terminal interface, resource system completeness, and dead code removal.

Articulated End State

This Legendary is fully realized when every feature, protocol, subsystem, and data type described in docs/specification.md has a functional implementation that matches the spec's defined behavior, interfaces, and contracts. Specifically:

The A2A protocol layer uses JSON-RPC 2.0 framing with all standard and extension methods operational
The LSP subsystem manages language server lifecycles and provides functional language intelligence
The ACMS context assembly pipeline is fully operational with all 10 pipeline components
All CLI commands produce output through the OutputSession framework with spec-conformant envelopes
The TUI provides a Textual-based interactive interface with all spec-defined features
All 34 spec-defined resource types are registered (24 physical + 1 subtype + 9 virtual)
All 12 ResourceHandler protocol methods are implemented
All stub/ghost packages are either implemented or cleanly removed
No orphaned build artifacts remain in the source tree

Child Epics

#933 Epic: A2A Protocol Compliance
#934 Epic: LSP Runtime Implementation
#935 Epic: ACMS Context Assembly Pipeline
#936 Epic: Output Rendering Pipeline Integration
#868 Epic: TUI Interface, Modals and Persona System
#824 Epic: LSP Functional Runtime
#825 Epic: ResourceHandler Protocol Completion
#946 Epic: Stub Package Cleanup

Definition of Done

This Legendary is complete when all child Epics are closed AND the articulated end state is independently verified: every subsystem described in the specification has a functional, tested implementation that matches the spec's contracts and behavior.

## Background A systematic audit of the codebase against `docs/specification.md` revealed multiple areas where the implementation diverges from the specification. The specification is the authoritative source of truth (per CONTRIBUTING.md §Specification-First Development), and all discrepancies must be resolved by aligning the code to the spec. This Legendary groups all Epics whose primary purpose is closing a verified gap between the current implementation and the specification. It spans multiple milestones (v3.4.0 through v3.8.0+) and covers protocol compliance, language intelligence, context assembly, output rendering, terminal interface, resource system completeness, and dead code removal. ## Articulated End State This Legendary is fully realized when every feature, protocol, subsystem, and data type described in `docs/specification.md` has a functional implementation that matches the spec's defined behavior, interfaces, and contracts. Specifically: - The A2A protocol layer uses JSON-RPC 2.0 framing with all standard and extension methods operational - The LSP subsystem manages language server lifecycles and provides functional language intelligence - The ACMS context assembly pipeline is fully operational with all 10 pipeline components - All CLI commands produce output through the OutputSession framework with spec-conformant envelopes - The TUI provides a Textual-based interactive interface with all spec-defined features - All 34 spec-defined resource types are registered (24 physical + 1 subtype + 9 virtual) - All 12 ResourceHandler protocol methods are implemented - All stub/ghost packages are either implemented or cleanly removed - No orphaned build artifacts remain in the source tree ## Child Epics - #933 Epic: A2A Protocol Compliance - #934 Epic: LSP Runtime Implementation - #935 Epic: ACMS Context Assembly Pipeline - #936 Epic: Output Rendering Pipeline Integration - #868 Epic: TUI Interface, Modals and Persona System - #824 Epic: LSP Functional Runtime - #825 Epic: ResourceHandler Protocol Completion - #946 Epic: Stub Package Cleanup ## Definition of Done This Legendary is complete when all child Epics are closed AND the articulated end state is independently verified: every subsystem described in the specification has a functional, tested implementation that matches the spec's contracts and behavior.

Rows
Columns