Rebuild repository guidance and establish quality tooling - #1003
Merged
Conversation
Replace stale topology and workflow prose with concise ownership, validation, type-safety, verification, communication, and instruction-editing contracts for repository-wide agent work. Constraint: Commit only the root AGENTS.md; nested guidance and placeholder documentation remain out of scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep path-specific rules in the nearest nested AGENTS.md and avoid duplicating root guidance Tested: git diff --check; git diff --cached --check Not-tested: Linked placeholder documentation and ignored pre-push Skill are not included in this commit
Remove the legacy specs corpus, stale design exports, regression case archive, obsolete documentation tree, and repository Skill lock so the replacement documentation system can start from an explicit empty baseline. Constraint: Preserve .specify templates and repository Speckit Skills for future specification work Rejected: Incrementally reorganize the legacy corpus | user chose a zero-history documentation reset Confidence: high Scope-risk: moderate Reversibility: clean through Git for tracked files; ignored local artifacts are not Git-recoverable Directive: Rebuild documentation ownership and navigation from the DSH model before adding new project documents Tested: git diff --cached --check; staged scope inspection Not-tested: Documentation links may remain unresolved until the replacement hierarchy is created
Align repository and subsystem guidance with the current ownership model, then add reproducible backend and frontend quality tools so contributors can run the documented checks locally. Constraint: Preserve existing product behavior and introduce no runtime dependencies. Rejected: Format or lint the entire existing frontend in this change | the baseline contains over one thousand lint findings and broad formatting churn would obscure the tooling change Confidence: high Scope-risk: narrow Reversibility: clean Directive: Treat current Pyright, ESLint, and Prettier findings as an explicit adoption baseline; tighten or fix them in reviewed increments Tested: frontend npm test (122 passed); frontend npm run build; Pyright 1.1.411 invocation; uv lock --check; ESLint and Prettier configuration loading; git diff --check Not-tested: Full backend pytest suite; existing Pyright, ESLint, and Prettier findings are not resolved
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.
Summary
Validation
Existing baseline findings
Not tested
This PR introduces and documents the quality harness without mixing in broad source cleanup or formatting churn.