AGENTS.md — Experimental packages

These rules supplement the package rules. The experimental publication decision owns the publication policy; the Agent Teams package decision owns dependency isolation and promotion rationale.

A package belongs here only when its complete public contract is experimental or internal-only. An experimental option inside a release package stays with its owning product role.
Every package here uses the @deepseek-ai/dsh-experimental-* npm prefix and joins the dsh release family by default: omit private and set publishConfig.access: public. Only directories in PRIVATE_EXPERIMENTAL_PACKAGE_DIRECTORIES in the publication policy stay private: set private: true and omit publishConfig.
Release packages and apps outside this group must not name experimental packages in dependencies, optionalDependencies, or peerDependencies. Default-product isolation also checks transitive installations, runtime imports, and shipped compositions in CI. Experimental packages may depend on release packages and each other. Tests may use experimental packages through devDependencies; examples may load them explicitly.
Experimental status does not relax engineering, security, documentation, lifecycle, testing, invariant, or snapshot requirements.
Publishing an experimental package does not promote it or add a stability promise. Promotion moves a package to its product-role group and removes experimental- from its npm name; update every import and configuration row atomically, then review its public contract, limitations, test evidence, release payload, runtime dependents, and named stable owner.