Define paid pilot transaction and private handoff

[fly1d]

Closes #10

Outcome

Makes the first three paid pilots operable without inventing an invoicing entity or publishing personal/payment information.

Changes

• disclose personal WeChat Pay / Alipay collection and no-invoice status before application
• let applicants self-identify invoice and corporate-payment blockers
• create a one-customer-per-private-repository handoff process using a verified private template
• add a written pre-payment confirmation covering scope, dates, payment, invoice status, data deletion, cancellation, and refunds
• prohibit customer data, contact details, payment QR codes, screenshots, transaction IDs, and credentials in GitHub
• document read-only collaborator invitations and post-acceptance access checks

External setup completed

• created fly1d/rabbitmq-guard-pilot-template
• GitHub reports the template repository as private and is_template=true
• its Issue Form YAML parses successfully
• it currently has no external collaborators
• template clarification was reviewed and merged through its own PR build(deps): bump actions/checkout from 4 to 7 #1

Risk

Medium. This does not change diagnostic code, but it defines payment disclosures and customer access. The public application remains intentionally non-confidential. Each qualified applicant receives a separate private repository with read-only access; customer data and payment data remain outside GitHub.

The repository does not claim legal/tax compliance or provide an invoice. Before collecting money, the service provider must personally verify platform and local tax requirements.

Verification

• make verify (44 tests)
• make smoke
• make package-smoke
• all repository YAML parsed
• private template Issue Form YAML parsed from GitHub
• public repository secret-pattern scan returned no matches
• private template visibility and template status verified through GitHub API
• diff whitespace check passed

Rollback

Revert this documentation commit and disable or archive the private template before accepting applications under a different payment model.

[fly1d]

Code review completed against 08d5c97 after all required checks passed.

No blocking findings.

Reviewed specifically:

• The public offer now states before application that the service is personally provided, accepts personal WeChat Pay or Alipay, cannot issue an invoice, and does not accept corporate payment. It does not represent a payment record as an invoice or invent an invoicing entity.
• The public Issue Form collects only fit and commercial constraints. It explicitly prohibits names, contact details, customer identifiers, logs, snapshots, bundles, payment QR codes/screenshots, and credentials.
• Qualified applicants receive isolated private repositories created from a template verified by the GitHub API as private and template-enabled. The documented invite grants pull only and checks pending invitations and external collaborators.
• The private repository is limited to written scope/date/refund/data-deletion confirmation and WeChat handoff. Customer diagnostics and payment details remain outside GitHub.
• The pre-payment template defines the offer, exclusions, version, start/end dates, deletion date, cancellation/refund behavior, and no-invoice status before payment.

Residual risk: personal collection and no invoice will exclude some business buyers. That is made explicit and tracked as a commercial validation result. The service provider must still personally verify payment-platform, local tax, identity, and record-retention requirements before collecting money; these cannot be established by repository automation.