[kingsleydon]

Summary

Add complete Agent Plugin packages for the requested Sui ecosystem partners. Each plugin is built from its own immutable upstream commit; plugin boundaries are preserved, and content is not removed because another plugin offers a similar or identically named Skill.

Plugin	Upstream-faithful contents
Cetus	Existing package with all 3 upstream Skills: Aggregator, CLMM, and DLMM
NAVI	Both upstream top-level Skills, including nested bridge, DCA, lending, and swap guidance
Aftermath	All 3 upstream Skills plus the official hosted aftermath-api MCP
Scallop	All 22 upstream Skills, shared references, and all 3 expert agents
t2000	All 14 upstream Skills, shared AGENTS.md guidance, and hosted OAuth MCP
Walrus	All 12 primary upstream Skills plus the 2 independently installable Sites portal/publishing Skills documented by Walrus

The existing Sui package becomes sui@0.2.0 while retaining all 21 Skills. The version bump only repairs the two existing Walrus Sites links after their standard top-level projection; it does not deduplicate or remove upstream content.

Upstream fidelity

• every mapped Skill target name equals the pinned upstream name frontmatter
• descriptions use restrained wording from upstream repository descriptions, READMEs, or manifests
• author, homepage, repository, license, and publisher fields are traceable to upstream sources
• Aftermath's aftermath-api name and URL match its official MCP documentation
• t2000's MCP name and URL match its upstream README and t2000-connect Skill
• NAVI's LICENSE is copied from its pinned commit and recorded in SOURCES.json
• Aftermath and Walrus/Sui path changes use exact occurrence-counted replacements so renamed or hoisted Skills retain valid internal links

Plugin keys, Store category, compatibility runtimes, and Store package versions are Store-owned registry fields. Skill names and bodies remain upstream-owned.

Deterministic normalization

Source-package recipe schema 2 keeps the final Agent Plugins and Agent Skills validators strict while supporting audited partner packages:

• copy pinned shared files and directories
• preserve unknown upstream frontmatter fields as string metadata under upstream.<field>
• serialize non-string metadata values as canonical JSON strings
• apply exact text replacements with required occurrence counts
• reject declared frontmatter normalization that makes no semantic change
• record every mapping and transformation in the artifact's SOURCES.json

There are no partner-specific branches in the builder, install hooks, runtime downloads, custom authentication fields, or relaxed final validation.

Independent review

A read-only Paseo Fable 5 xhigh review compared the PR artifacts against all six pinned upstream repositories and official Aftermath/Walrus documentation. Its merge-time findings were addressed:

• repaired all 8 missed Aftermath references after the upstream-declared Skill name projection
• moved NAVI LICENSE into pinned recipe provenance
• exposed both Walrus Sites subskills and repaired their links
• added fail-loud checks for stale normalization and replacement declarations
• aligned Store descriptions with upstream wording

Verification

Run in an ephemeral Docker copy of the repository:

• python3 scripts/validate.py
• python3 -m unittest discover -s v2/tests -v (18 tests)
• python3 v2/scripts/source_package.py --check --artifacts /artifacts
• python3 v2/scripts/validate.py
• artifact checks for Aftermath link closure, NAVI LICENSE provenance, all 14 t2000 Skills, all 14 Walrus Skills, all 21 Sui Skills, and valid hoisted Sites links
• git diff --check