docs/CONTRIBUTION_STRATEGY.md

Contribution Strategy

Codex contribution is part of the hackathon strategy. Keep the history clear, useful, and easy for judges to inspect.

Rules

• Use small commits with plain messages.
• Keep planning, scaffolding, model integration, UI, tests, and submission polish in separate commits.
• Do not squash the whole project into one final commit.
• Preserve Codex-attributed commits in GitHub history.
• Reference the relevant plan file in commit bodies when useful.

Suggested Commit Sequence

1. Initialize BugLens planning scaffold
2. Add verified stack foundation
3. Implement validated bug report schema
4. Add deterministic render exports
5. Build mock Gradio workflow
6. Wire MiniCPM observation pipeline
7. Add Modal inference endpoint
8. Polish custom BugLens UI
9. Add examples, tests, and README submission links

Why This Matters

The plan targets Best Use of Codex. A clean contribution history shows Codex was used holistically: planning, scaffolding, schemas, tests, backend integration, UI, and deployment support.