Repository navigation
docs: prepare the first voluntary developer beta testing round - #5
Merged
Merged
Conversation
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.
Prepare an initial round for 10 consenting external developers without contacting testers, enrolling participants or collecting feedback yet.
Add BETA_TESTING.md with current scope, prerequisites/source installation, first scan, literal reproducible fixture preparation, seven testing scenarios, limitations and an unsent invitation draft. Existing fixtures exercise all five providers, a known dynamic-import miss, declared versus recorded version evidence, scoped compatibility, terminal/JSON readability and input errors. Extend FEEDBACK.md with seven optional questions and link the guide from README.
Use actual enabled Issues/Discussions categories; security reports remain confidential through SECURITY.md. Public profile/post visibility and sanitization requirements are explicit. Founder opening of the round, consent and handling/responder decisions precede outreach or collection. No automatic contact, telemetry, signup, email or repository settings change.
Validation: literal documented fixture-generation and scan commands executed; expected five-provider detection, known miss, Stripe recorded version/rename assessment, OpenAI unknown installed version/model assessment and errors verified. Targets unchanged; no scanned code executed or target dependencies installed. Frozen offline reinstall with trusted existing store, build, ordinary package and empty-cache offline beta installation passed. Local doc links, YAML-existing channels, feedback questions, metadata/prerequisites, unchanged scanner/dependencies/security/license/workflow and exact three-Markdown-file diff checked. Fresh network install was verified in Task 054 with the unchanged dependency graph. The unchanged 358-test scanner suite was not unnecessarily repeated locally; hosted Ubuntu/macOS CI must pass.
The new main-branch guide links become available after founder-reviewed merge. Leave this PR unmerged. No testers contacted or data collected.