YipYap (Language) v0.3.3

YipYap (Language) v0.3.3

Signed sequence-6 release of the provider-neutral YipYap (Language) plugin.
This release moves the local connector to the compile-time future-production
API-origin profile at https://api.magneum.co, binds credentials to that exact
profile, and flattens the advertised My Lexicon read schema so strict MCP
clients accept the full tool list.

Included

• one compiled API-origin profile, future-production, reaching only
  https://api.magneum.co through the fixed api-magneum-co-local-gateway.v1
  routes, with no runtime selector, endpoint override, redirect, fallback,
  mirror, or dual write;
• a separate mode-0600 profile-bound credential file per provider, and no
  legacy environment-token forwarding in the provider manifests;
• an advertised providerReadLexiconProjection input schema that strict MCP
  clients accept, so the packaged connector loads on current Claude Code hosts;
• the unchanged logical surface: one explicit pairing bootstrap plus the same
  five authenticated provider callables and the same connector-interface
  packet;
• the same read-first teaching cycle, five provider event kinds, bounded
  best-effort proposal path, and exact read-only yip new, yip new day,
  yip new week, and yip summary commands; and
• a promotion policy under which one explicit, consequence-aware owner approval
  may cover both the new default and every non-deleted production installation.

Upgrade boundary

The v0.3 line changes the runtime contract, so immutable v0.2.1 and v0.2.2
updaters correctly reject this release. That refusal is intentional. Move to
v0.3.3 through a fresh install or a provider-native or YipYap app-controlled
reinstall of this signed immutable release. Existing installations remain on
their current profile until the owner-approved promotion; nothing migrates
silently, and legacy credential bytes are never copied, retagged, or reused.
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. The connector reads only its own
profile-bound credential file and never a credential for another profile.

Verification

The clean pushed source passes the repository validator and its full test suite
under Node 22.23.1, including exact-origin, credential-binding, no-fallback,
legacy-isolation, update, and API-origin staging suites. Strict Claude plugin
and marketplace validation 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 installation or activation, account
connection, pairing, Learning Mode, restart/new-root acceptance, promotion or
migration of any installation, rollback, provider-directory submission, or a
public directory card. Those remain separate owner and provider evidence gates.