deepseek-harness/packages/experimental/AGENTS.md

AGENTS.md — Experimental packages

These rules supplement the package rules. The experimental Agent Teams package decision owns the 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. Packages are private by default and omit publishConfig; the five Agent Teams packages are explicit public exceptions that keep their experimental names, set publishConfig.access: public, and join the dsh release family.
• Release packages and apps outside this group must not name experimental packages in dependencies, optionalDependencies, or peerDependencies. 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 explicit exception 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.