Repository navigation
docs(issues): [#2475] add issue specification for #2475 - #2476
Merged
josecelano merged 1 commit intoOct 8, 2026
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The documentation promotion is complete, internally consistent, and all changed relative links resolve.
0 open findings
What changed in this PR
Promotes the reviewed #2475 bug specification from draft to an open EPIC #1669 subissue.
Changes:
- Updates issue metadata, checkpoints, and verification evidence paths.
- Links #2475 from the EPIC and coupling report.
- Preserves historical draft references only in immutable review records.
| File | Description |
|---|---|
ISSUE.md |
Promotes and numbers the specification. |
manual-verification-evidence.md |
Updates the primary-spec reference. |
EPIC.md |
Registers #2475 and its open specification. |
workspace-coupling-report-2026-10-06.md |
Links finding 3 to #2475. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…-tool name fix Move the reviewed draft to docs/issues/open/ as issue torrust#2475, a subissue of EPIC torrust#1669, and point the EPIC and the 2026-10-06 coupling report at it.
josecelano
force-pushed
the
2475-1669-coupling-tool-resolve-lib-names-and-renames-spec
branch
from
October 8, 2026 06:36
4d4157f to
df57701
Compare
Member
Author
|
ACK df57701 |
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-only PR for #2475 (subissue of EPIC #1669): promote the coupling-tool bug draft, reviewed in PR #2462, to an open issue spec. No code changes; implementation starts on
2475-1669-coupling-tool-resolve-lib-names-and-renamesafter this merges.Related to #2475
Related to #1669
Changes
docs/issues/open/2475-1669-coupling-tool-resolve-lib-names-and-renames/(moved fromdocs/issues/drafts/1669-coupling-tool-resolve-lib-names-and-renames/):ISSUE.md: issue number in the title and frontmatter (github-issue,spec-path,branch,status: planned), the three creation checkpoints ticked, and a progress-log entry. The bug content is unchanged from the reviewed draft.manual-verification-evidence.md:issue-specpoints to the new path; the R1 reproduction record is unchanged.docs/issues/open/1669-overhaul-packages/EPIC.md: the quick list and Details table link Coupling tool misses renamed dependencies and custom library names (EPIC #1669) #2475, the Details row and Specs Index link the open spec, plus a progress-log entry.workspace-coupling-report-2026-10-06.md: finding 3 links Coupling tool misses renamed dependencies and custom library names (EPIC #1669) #2475 and its open spec instead of the draft.Pre-commit and pre-push checks passed.