Independent acceptance organization for cliptown.

Clipboard fidelity, SDK/API, UI, extension, sync, device coverage, and Memebank interoperability.

Pull requests run deterministic harness checks. Emulators, desktop matrices, live APIs/providers, databases, chaos, scale, and soaks are scheduled/manual. Missing upstreams or credentials are blocked readiness—not false passes or product regressions.

• GitHub Project: cliptown-test-project
• Linear planning project
• Detailed project-routing contract

GitHub owns code and delivery evidence; Linear owns planning and dependencies. The linked organization Project provides the cross-repository execution view.

• API and SDK contract conformance
• Browser and extension behavior
• CLI compatibility
• Desktop lifecycle and clipboard behavior
• Android and iOS emulator coverage
• Cross-device sync and recovery behavior
• Rich-content and Memebank interoperability
• Security-boundary and failure-path testing

All generated pull-request workflows use least privilege, immutable action pins, and no persisted checkout credential. Integration workflows are gated by organization variables and credentials.

• Canonical Linear project: https://linear.app/denman/project/githubcomcliptown-test-8157daa8a324
• Organization defaults: https://github.com/cliptown-test/.github
• Canonical agent policy: https://github.com/cliptown-test/.github/blob/main/agents.md
• Security policy: https://github.com/cliptown-test/.github/security/policy

Repositories in this organization use semantic conflict resolution with 3–10 relevant prior commits when useful, full cross-repository context, pull-request delivery, and a hard automated-agent denylist for destructive or history-rewriting operations.

cliptown-test declares repository roles, dependency edges, cross-organization capabilities, deployment ownership, and the git-submodule/Zed-package contract:

• Human-readable map
• Machine-readable manifest
• JSON Schema

The public registry withholds private repository names and edges.