Yip-Yap Language v0.2.1

Yip-Yap Language v0.2.1

Signed sequence-2 release of the provider-neutral Yip-Yap Language plugin.
This release adds the app-led pairing path needed for the first real connected
installation while preserving fail-closed L0 behavior.

Included

• one explicit yipyapPair bootstrap that redeems the short, single-use code
  created by the Yip Yap app;
• five fixed authenticated provider operations, with ordinary rendering limited
  to the ordered status, settings, and teaching-context reads;
• owner-only connector configuration, atomic credential replacement, per-call
  rereads, config-first precedence, symlink and permission refusal, and no retry
  after an ambiguous single-use redemption;
• exact MCP titles and safety annotations;
• strict Claude and Codex package metadata, one shared Skill, and truthful
  supported-host startup claims;
• package-local README, setup, reconnect, revocation, and troubleshooting
  instructions; and
• deterministic sequence-2 release inventory. Provider reviewer cases are
  prepared in the private release authority; they are not shipped in the
  public package.

Upgrade boundary

Immutable v0.2.0 exact-pins the pre-pairing connector-interface packet. Its
updater therefore correctly rejects v0.2.1. Cross this one-time boundary with a
fresh install or a provider-native or Yip Yap app-controlled reinstall of the
signed immutable v0.2.1 release. Do not weaken the old pin or edit an installed
package. Later same-contract releases continue through the signed sequence.

Security and privacy

The pairing code is not a session credential. The connector never returns the
redeemed credential to the model, places it on a command line, or stores it in
the versioned plugin. Conversation text, files, prompts, transcripts, repository
context, raw account identities, and provider-session identifiers remain outside
the connector boundary. Every incomplete, stale, revoked, malformed, null, or
incompatible state fails the complete reply closed to effective L0.

Verification

The release source passes the repository validator and 93/93 tests, including
27/27 focused connector and pairing cases. The plugin also passes the strict
Claude package validator and OpenAI Codex plugin validator. The release ceremony
requires two independently sourced signing-key copies to produce byte-identical
expanded trees, manifests, detached signatures, and deterministic archives.

Not claimed

This release does not claim a live owner pairing, provider-directory approval,
an OpenAI production HTTPS MCP endpoint, universal lifecycle-hook support,
provider-native automatic apply, installed-host rollback, or language cutover.
Those remain separate app, provider, and owner evidence gates.

The repository-hosted release intentionally comes first: it is the immutable
artifact the app-led install and pairing walkthrough will exercise. Successful
installation, pairing, and connected-session evidence must be recorded after
publication and cannot be inferred from these signed bytes.