Context
The local DevPlan build already has a richer RDLeader slice than the current public baseline: runtime dispatch / result collection, QA ops checks, browser validation, employee-agent onboarding, project group routing, and external-blocker reporting.
The public repository should not publish the raw DevPlan artifacts as-is because some local logs and screenshots can contain private workspace paths, organization-specific identifiers, QR onboarding artifacts, or live integration evidence.
Public release checklist
Sponsorware candidates
- Public demo video / landing page
- Sanitized QA evidence bundle
- Employee-agent onboarding docs
- Runtime endurance deep dive
- One-click local demo reset script and screenshots
Support page: https://happysnaker.github.io/support/
10-second support router
If you are not sure whether to tip, inspect proof, buy a review, or fund public-release sanitization, start here: https://happysnaker.github.io/support/#sponsor-router. Support does not imply RDLeader reuse rights.
Support / outreach qualification
Before posting a sponsor/support ask, tester request, or external follow-up, use the sponsor conversion scorecard: https://github.com/happysnaker/happysnaker/blob/master/docs/sponsor-conversion-scorecard.md
Classify the situation as Hot / Warm / Nurture / No-send first. No-send blocks generic donation or proof bumps when timing, proof, privacy, or license posture is weak.
Do not paste private logs, credentials, QR codes, payment screenshots, internal URLs, or raw live integration output in public issues.
Context
The local DevPlan build already has a richer RDLeader slice than the current public baseline: runtime dispatch / result collection, QA ops checks, browser validation, employee-agent onboarding, project group routing, and external-blocker reporting.
The public repository should not publish the raw DevPlan artifacts as-is because some local logs and screenshots can contain private workspace paths, organization-specific identifiers, QR onboarding artifacts, or live integration evidence.
Public release checklist
Sponsorware candidates
Support page: https://happysnaker.github.io/support/
10-second support router
If you are not sure whether to tip, inspect proof, buy a review, or fund public-release sanitization, start here: https://happysnaker.github.io/support/#sponsor-router. Support does not imply RDLeader reuse rights.
Support / outreach qualification
Before posting a sponsor/support ask, tester request, or external follow-up, use the sponsor conversion scorecard: https://github.com/happysnaker/happysnaker/blob/master/docs/sponsor-conversion-scorecard.md
Classify the situation as Hot / Warm / Nurture / No-send first. No-send blocks generic donation or proof bumps when timing, proof, privacy, or license posture is weak.
Do not paste private logs, credentials, QR codes, payment screenshots, internal URLs, or raw live integration output in public issues.