Dependency Absorption

How an absorption is run. Whether a package should be absorbed at all — the three costs, the admission test, the stop list, what an adapter is, the standard and the triage verdicts — is apps/web/content/docs/architecture/dependency-admission.md, and nothing here restates it.

Settled — do not re-propose

• A parity gap left because our app does not call that half. An adapter is absorbed as a package of its own, and a package missing the surface it replaced is a fork with gaps (apps/web/content/docs/architecture/dependency-admission.md, "The standard an absorption meets").
• Porting a shape an engine has deprecated, for parity. Parity is with the engines' current surface, and the replacement carries no debt the upstream package kept for its older users (apps/web/content/docs/architecture/dependency-admission.md, "The standard an absorption meets").
• Recording the triage in the commit body alone. The next reader arrives from a stranded upstream link in our code or a search, not from git log; the verdicts live on the package's docs page (references/package-shape.md).
• Skipping the closed issues. A closed issue is where a fix the replacement must keep, or a workaround our code still carries, is explained (references/upstream-audit.md).

Rules

• The upstream audit runs before any code is written — every issue, open and closed, read with its comments (references/upstream-audit.md).
• Every verdict carries its evidence: a reproduction for a defect, a test for a feature, the named owner for out of scope, the answering link for a false positive (references/upstream-audit.md).
• An in-scope defect's regression test fails against the upstream package first, and names the issue in its title (references/upstream-audit.md).
• An issue split across the adapter and a neighbour gets both verdicts — the adapter's part fixed, the neighbour's part out of scope with our constraint written on the page owning our side.
• An absorbed adapter is a workspace package built to the file-organization skill's references/new-package.md, with its own docs section carrying the Upstream table (references/package-shape.md).
• The residue sweep lands in the commit that deletes the catalog entry (references/residue-sweep.md).

Reference pages

• references/upstream-audit.md — when reading a package's tracker, or giving an issue its verdict.
• references/residue-sweep.md — when the last import of the absorbed package is about to go.
• references/package-shape.md — when creating the replacement package, its README or its docs section.