Problem
STATUS.md is checked into the repo containing personal developer session notes, PR backlogs, and internal operational data. New users and testers cloning AIPass receive this file with all of that content pre-populated.
Expected behavior
STATUS.md should ship as an empty (or minimal placeholder) file. It is auto-generated by drone @prax status sync and should build up from the local system — it has no business being pre-filled in the repo with developer-specific information.
Suggested fix
- Reset
STATUS.md to a blank or stub file before any public-facing commit/release
- Consider adding a note at the top clarifying it is auto-generated and gitignore it, or add a
.gitignore rule if it should never be tracked
- Alternatively, ship a
STATUS.md.example and gitignore the real file
Context
Discovered during Windows 10 fresh-clone test. The file contained internal session notes, PR numbers, and operational data that should not be visible to new users or contributors.
Problem
STATUS.mdis checked into the repo containing personal developer session notes, PR backlogs, and internal operational data. New users and testers cloning AIPass receive this file with all of that content pre-populated.Expected behavior
STATUS.mdshould ship as an empty (or minimal placeholder) file. It is auto-generated bydrone @prax status syncand should build up from the local system — it has no business being pre-filled in the repo with developer-specific information.Suggested fix
STATUS.mdto a blank or stub file before any public-facing commit/release.gitignorerule if it should never be trackedSTATUS.md.exampleand gitignore the real fileContext
Discovered during Windows 10 fresh-clone test. The file contained internal session notes, PR numbers, and operational data that should not be visible to new users or contributors.