docs: link SPEC.md T18 to the internal/ui design issue#75
Merged
Conversation
Refs #74. Keeps the spec's task list traceable now that the internal/ui scope has an actual tracked issue with a chosen approach (Charm stack: lipgloss/bubbletea/huh) rather than just a bare TODO.
|
✔️ e1102bf - Conventional commits check succeeded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SPEC.md's T18 row (design + implement internal/ui output layer) now cites#74alongsideV2, since that issue now has the actual chosen approach (Charm stack: lipgloss/bubbletea/huh) and package layout scoped out.Test plan
Refs #74 (not closing — the feature itself isn't implemented yet, just scoped).
🤖 Generated with Claude Code