Repository navigation
YipYap (Language) v0.2.2
YipYap (Language) v0.2.2
Signed sequence-3 release of the provider-neutral YipYap (Language) plugin.
This release restores the conversational AI teaching loop, tightens the
provider event boundary, and adds exact read-only My Lexicon recency and
summary commands while preserving the v0.2.1 connector-interface contract.
Included
- exactly five provider event kinds:
item_proposed,item_edited,
item_archived,item_rendered, andplayback_completed, with response and
answer-reveal events structurally absent; - multilingual teaching from the verified active language/script, stored
level, dose, supplied vocabulary, and introduction cap; - a bounded best-effort proposal path for generated vocabulary membership and
provenance only—never exposure, correctness, recall, mastery, or known
status; - binding-coherent local read/proposal guards and the identity-free,
current-reply workflow handle required by the remote MCP profile; - exact read-only
yip new,yip new day,yip new week, andyip summary
commands through the existing lexicon-read operation and scope; - strict rejection of fuzzy, extra-argument, retired-command, malformed, and
unsupported-version forms; and - the formal product name
YipYap (Language)with short brandYipYap.
Upgrade boundary
v0.2.2 retains the exact connector-interface packet pinned by v0.2.1, so a
trusted v0.2.1 installation may accept signed sequence 3 through the normal
update rules. The intentional v0.2.0-to-v0.2.1 controlled-reinstall boundary
is unchanged. Successful apply still stops at restart-required; activation
requires a complete provider restart and a new root task.
Security and privacy
Conversation text, prompts, transcripts, files, repository context, account
identities, provider-session identifiers, credentials, and learner evidence
remain outside the connector payload. Recent and summary reads expose only the
bounded personal My Lexicon fields defined by their closed schemas. Migrated
baseline vocabulary does not become personal membership unless it is
independently proposed through an authorized path.
Verification
The clean pushed source passes the repository validator and 208/208 tests under
Node 22.23.1, including 85/85 focused recent/summary cases. Strict Claude
plugin and marketplace validation, the official Codex plugin validator, and
the official Skill validator pass. Two independently sourced signing-key
copies produced byte-identical expanded trees, manifests, detached signatures,
and deterministic archives.
Not claimed
Publication does not prove provider activation, account connection, pairing,
Learning Mode, live recent/summary output, restart/new-root acceptance,
rollback, provider-directory submission, review approval, or a public
directory card. Those remain separate owner and provider evidence gates.