Repository navigation
Clean the public docs for strangers - #18
Merged
Merged
Conversation
The repository went public with docs written for its own development. Before anyone is pointed at it, they should read clean to someone who was not there. Internal material is gone: owner quotes, the private files that motivated the attachments feature, other organizations' workspaces, live-workspace sizes, and personal workflow command names. The three phase-gate audits and five finished plans are deleted. They cited PR numbers and commit hashes from the pre-release repository, which now point at unrelated public PRs or at nothing. The roadmap's Completed section carries what they delivered, without those references, and git keeps the files. Contradictions and stale wording are fixed: the roadmap claimed JSONL drops the files array, when it carries the rendered file line and no structured metadata; the README status said v0.2; pyproject said v0.1; Phase 3.1 still waited on a publication decision already made; and the Phase 2.0 plan cited seeds from a deleted audit, now numbered in the roadmap. The README notes why whoami lists identify and adds attachment download to what is not built yet.
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.
Docs only. No code or behavior change, no history rewrite. Offline suite: 512 passed. All internal links and anchors resolve.
1. Internal-only references
2. Stale PR numbers and commit ranges
docs/assessments/(three phase-gate audits) and five finished plans (slackline-read-mvp,read-only-mvp-gate-fixes,gate-rerun-fixes,public-release-prep,slackline-skill). They cited pre-release PRs and commits that are not in this repository's history. Git keeps them.Seed-Nnow cites the numbered seed list in the roadmap, and its PR references are reworded.3. Contradictions
[file: name (type, size)]line in the message text, nothing dropped, but no structured file metadata and no download.4. Stale wording
pyproject.tomlcomment: "One executable in v0.1" to "One executable today".whoamisample: kept as printed (it matches real output), plus a note that the manifest does not requestidentify; Slack grants it to every user token.Checked and kept
pyproject.toml.