Independent acceptance organization for zed-pkg.
Black-box certification for Zed resolution, storage, adapters, migration, registry, concurrency, Nix, OCI, offline replay, and supply-chain safety.
- Canonical Linear project:
github.com/zed-pkg-test - Canonical GitHub Project:
zed-pkg-test-project(project 1) - Cross-system registry:
zed-pkg/zed-docsdoc 33 - Machine-readable mapping:
github-linear-project-registry.toml - Linear registry document:GitHub organization → Linear project → GitHub Project registry
Project 1 is the verified canonical organization board. Fleet reconciliation keeps its exact title, active state, governance issue, and routing documentation aligned with the Linear project.
| Repository | Class | Readiness | Primary dependency path |
|---|---|---|---|
zed-pkg-e2e | aggregate lifecycle and external canaries | ready | matrix |
recursive-diamond-graph | package-manager | ready | zed |
recursive-cycle-detection | package-manager | ready | zed |
concurrent-install-locking | chaos/fault injection | ready | matrix |
overtake-submodule-migration | interoperability | ready | git-submodule |
nix-export-interop | Nix interoperability | ready | matrix |
manager-interop-e2e | environment-manager interoperability | ready | matrix |
oci-multiplatform-e2e | OCI interoperability | ready | matrix |
offline-cache-e2e | offline replay | ready | matrix |
security-adversarial-e2e | security/adversarial | ready | matrix |
first-install-manifest | package-manager | ready | matrix |
constraint-solver-blackbox | package-manager | ready | matrix |
registry-api-contract | API contract | ready | matrix |
registry-browser-e2e | browser E2E | ready | matrix |
security-path-traversal | security | ready | matrix |
Language fixture families include Node.js, Rust, Go, Python, Dart, Gleam, Erlang, Java, Kotlin, C#, Swift, polyglot packages, workspaces, submodules, subtrees, version conflicts, and deliberately adversarial package layouts.
This organization publishes workflow certification evidence, bounded failure diagnostics, checksums, and immutable replay inputs. A workflow artifact is not a production package or release merely because it was archived. Test workflows must not publish to package registries, releases, OCI registries, or binary caches unless that mutation is the explicit subject of a separately reviewed isolated test environment.
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 owns code and delivery evidence; Linear owns planning and dependencies. The linked organization Project provides the cross-repository execution view.
- Canonical Linear project: https://linear.app/denman/project/githubcomzed-pkg-test-e0b5db761974
- Organization defaults: https://github.com/zed-pkg-test/.github
- Canonical agent policy: https://github.com/zed-pkg-test/.github/blob/main/agents.md
- Security policy: https://github.com/zed-pkg-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.
zed-pkg-test declares repository roles, dependency edges, cross-organization capabilities, deployment ownership, and the git-submodule/Zed-package contract:
The public registry withholds private repository names and edges.