Skip to content

Public release checklist: sanitize DevPlan feature bundle #1

Description

@happysnaker

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

  • Split the DevPlan feature bundle into reviewable commits instead of one huge dump
  • Keep runtime endurance / stale recovery code, but publish only sanitized evidence
  • Keep QA ops panel, but redact private paths and live org identifiers in reports
  • Keep Feishu/Lark-style employee-agent architecture docs, but never publish app secrets, QR images, chat IDs, or open IDs
  • Add a small public demo page or screen recording using fake/demo identities
  • Add a sponsor-friendly roadmap table: what is free, what needs funding, and what a sponsor unlocks
  • Decide whether this repo is ready for an explicit license before broader promotion

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    public-packagingPublic-safe packaging and release preparationroadmapRoadmap and planned worksponsorshipFunding, sponsorship, and paid support

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions