fix: correct absolute /_core/ paths to relative (9 broken references) - #10
Open
Avicennasis wants to merge 1 commit into
Open
fix: correct absolute /_core/ paths to relative (9 broken references)#10Avicennasis wants to merge 1 commit into
Avicennasis wants to merge 1 commit into
Conversation
Every reference to _core/ in workspace-builder was written with a leading slash, so it resolves to the filesystem root rather than the repo root. `ls /_core` does not exist on any machine. This matters most in workspace-builder because it is the workspace that generates every other workspace: stage 03-scaffolding cannot reach the templates it scaffolds from, and stage 05-validation cannot reach the CONVENTIONS.md it validates against. 29 references across 6 files, rewritten to the correct relative depth: stages/*/CONTEXT.md -> ../../../../_core/ CLAUDE.md -> ../../_core/ references/conventions-*.md -> ../../../_core/ This matches the rest of the repo: the other 83 path references in Inputs tables are all relative, and _core/templates/stage-context-template.md writes the same paths without a leading slash. Verified by resolving all 29 rewritten references from each file's own directory: 29 resolve, 0 broken.
This was referenced Aug 19, 2026
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
1 participant
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.
Every reference to
_core/insideworkspace-builderis written with a leading slash, so it resolves to the filesystem root rather than the repo root.This is the one workspace where it bites hardest, because
workspace-buildergenerates every other workspace:stages/03-scaffoldingcannot reach the three templates it scaffolds fromstages/05-validationcannot reach theCONVENTIONS.mdit validates againstScope
29 references across 6 files, not just the Inputs tables:
stages/*/CONTEXT.md../../../../_core/CLAUDE.md../../_core/references/conventions-reference.md../../../_core/Why relative is the right form here
The other 83 path references in Inputs tables repo-wide are all relative, and
_core/templates/stage-context-template.mdwrites these same paths without a leading slash. The/_core/style is used by 9 refs, all confined to this one workspace.Verification
All 29 rewritten references were resolved from each file's own directory: 29 resolve, 0 broken.
Note
references/conventions-reference.mdline 3 is also touched by the rename PR. If both land, keep the relative path from this one and the ICM wording from that one. It is a one-line conflict.