chore: use DOC_ROOT for requests path and drop the consumer-repo reference - #62
Closed
poxet wants to merge 1 commit into
Closed
chore: use DOC_ROOT for requests path and drop the consumer-repo reference#62poxet wants to merge 1 commit into
poxet wants to merge 1 commit into
Conversation
Contributor
Author
|
Superseded by #64, which carries this change together with the version bump and the comment cleanup in a single PR. |
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.
Two corrections to
.claude/mission.md.1.
Incoming requestswas a literal pathEvery other reference in this file already used
$DOC_ROOT; this one line did not. A hard-coded path resolves on exactly one machine and silently finds nothing everywhere else — and "silently finds nothing" is indistinguishable from "nothing was pending", which is the failure mode that matters for a startup check.2. The Eplicta reference is removed
A Tharga project should not reference a consuming product's repository at all. External consumers file GitHub issues on this repo, and the outbound duty is a comment on that issue — not writing status back into their files.
This one was also already broken: the file it named does not exist, at that path or anywhere in the Eplicta checkout. Replaced with a line stating the actual channel, so the reference is not reintroduced later.
Related
The same policy is now written into
shared-instructions.mdunder Feature Requests (cross-project) → External consumers, and the "update any consuming project's request file" bullet in Closing a feature has been replaced by "comment on the GitHub issue".Nine other Tharga sub-projects still carry one or both of these problems — reported separately, not touched here.