# Use the preserved suite against current contracts

Checked 2026-10-28. The six rich upstream topics are complete source snapshots from `4beb46c0937ec9806960b5425be9ccd3ddc47533`, generated with source/output hashes. They retain conceptual depth, examples, tests and source history. Their imports, catalog, example numbering, agent names and CLI commands require current-host verification; installing this method grants no runtime, model, publishing or enrollment authority.

- **Foundation versus Core:** the preserved app/Foundation examples import `load_bundle` from `amplifier_core`. Current Foundation authoring documentation places bundle loading/composition in `amplifier_foundation`; use the installed exports and actual lifecycle signature. Do not copy either a remembered snippet or a source snapshot into production without resolving it.
- **Reusable behavior versus supporting root:** a reusable capability behavior adds its own tools, agents, hooks and context while preserving host provider, orchestrator/context policy and root instruction. The older definition “instruction overlay only, no tools” is too narrow. A supporting root may still be needed for namespace/resource anchoring; test actual resolution rather than removing roots categorically.
- **Session identity versus resumption:** a reused session ID alone does not establish durable history, current conversation state or context restoration. Inspect the selected host/context implementation and demonstrate resumption before claiming it.
- **Ownership versus dependencies:** the kernel/Foundation/app separation is useful. “Only Core” is a boundary against importing application/Foundation machinery into runtime modules, not a prohibition on justified ordinary libraries; inspect each actual module protocol and dependency graph.
- **Delegation and memory:** use the current CLI help and actually available expert agents. Memory is optional. A catalog reference to an agent, hook or bundle does not establish installation or authorize a provider call. Native runtime execution, setup and publication remain separate from method installation.
- **Helper scripts:** use `sh scripts/list_agents.sh --help` and `sh scripts/session_context.sh --help` from the installed skill folder. The upstream nested script paths delegate to those single canonical implementations. Tests use an isolated `AMPLIFIER_HOME`; cached listings and session metadata can be stale.

Primary sources: [current Foundation Bundle Guide](https://github.com/microsoft/amplifier-foundation/blob/81b9bb07eb8fa3b0be2f080fb560a3b203cb2ad1/docs/BUNDLE_GUIDE.md), [Core repository](https://github.com/microsoft/amplifier-core), and the actual installed source/help/tests for the host being extended. Documentation comparison establishes guidance and known caveats, not a real integration or provider result.