Remove the internal forge hostname and add the doc manifest — this repo's main is un-gateable without them - #390
Merged
Merged
Conversation
Two pre-existing lint errors made this repo's main un-gateable, so no branch could reach green regardless of its own quality. Found while gating unrelated work. CONTRIBUTING.md carried an internal .lan hostname in three places -- the forge's address written into tracked content. That address is per-box state, not a property of this repository, so it is now referred to as <forge> with a note saying where a reader gets the real value: their own git remote, or the kanon MCP binding the session-start probe reports. Removing a fact without saying where it lives would just move the problem. This matters beyond the lint: an internal hostname in a tracked tree is exactly the class of content that must not survive into a public repository, and this repo is in scope for the fleet's public-flip work. docs/MANIFEST.toml did not exist while docs/ did. Seven entries, one per document, classified by reading each rather than by pattern: two decision records, four authored, and the mesh config example. Three are marked non-evergreen with the reason stated in place -- the lexicon calls itself a living registry, the reference-store doc describes an arrangement built on a crate that is still planned, and the config example is a snapshot of supported hardware. The archive subtree is deliberately absent. Git is the archive, and a second index of superseded documents is a copy of what history already guarantees.
The first version deliberately omitted docs/archive/ on the reasoning that git is the archive and a second index of superseded documents duplicates what history already guarantees. That reasoning is right in general and answers a different question than the rule asks. STANDARDS/doc-manifest-orphan asks only whether every file under docs/ is accounted for, because an unlisted file is indistinguishable from one nobody noticed. Listing the two archived documents as non-evergreen answers that without claiming they are current.
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.
fix(docs): remove the internal forge hostname and add the doc manifest
Two pre-existing lint errors made this repo's main un-gateable, so no branch could
reach green regardless of its own quality. Found while gating unrelated work.
CONTRIBUTING.md carried an internal .lan hostname in three places -- the forge's
address written into tracked content. That address is per-box state, not a property
of this repository, so it is now referred to as with a note saying where a
reader gets the real value: their own git remote, or the kanon MCP binding the
session-start probe reports. Removing a fact without saying where it lives would just
move the problem.
This matters beyond the lint: an internal hostname in a tracked tree is exactly the
class of content that must not survive into a public repository, and this repo is in
scope for the fleet's public-flip work.
docs/MANIFEST.toml did not exist while docs/ did. Seven entries, one per document,
classified by reading each rather than by pattern: two decision records, four
authored, and the mesh config example. Three are marked non-evergreen with the reason
stated in place -- the lexicon calls itself a living registry, the reference-store
doc describes an arrangement built on a crate that is still planned, and the config
example is a snapshot of supported hardware.
The archive subtree is deliberately absent. Git is the archive, and a second index of
superseded documents is a copy of what history already guarantees.