YipYap (Language) v0.3.9

Signed release v0.3.9 / sequence 12. Assets: manifest.json, manifest.sig, yipyap-language-0.3.9.tar, yipyap-language-plugin-0.3.9.tar. Verify with the pinned public key.

YipYap (Language) v0.3.8

YipYap (Language) v0.3.8

Signed sequence 11 release for the existing future-production API-origin profile.

• Clarifies local Codex and Claude Code setup after a one-time pairing code is refused, without changing authorization behavior.
• Applies the L4 word dose to the final rendered reply, including progress updates, while keeping commands and other protected text outside the teaching mix.
• Keeps the provider-neutral teaching Skill and packaged learning contracts aligned across both manifests.

The stable signed update index and public main now select v0.3.8. Provider installation and activation still require a separate host update and full restart.

The release contains the signed manifest, its signature, the release archive, and the plugin-root archive.

YipYap (Language) v0.3.7

YipYap (Language) v0.3.7 ships the package rights notice inside the installed plugin and declares the manifest license as LicenseRef-YipYap-Rights-Notice. It adds the static "YipYap help" command with its footer hint, reads connection status exactly once per reply, and renders the teaching footer as the final line after any vocabulary proposal.

Node.js 22.23.1 or later must still be available on the host PATH. Teaching behavior, account contracts, API-origin selection, and publisher metadata are unchanged.

This signed release is promoted to the stable channel and GitHub latest. Installing this version and restarting the provider are separate steps.

Assets include the signed manifest and its detached signature, the complete release archive, and the plugin-root archive. Release sequence: 10.

YipYap (Language) v0.3.6

YipYap (Language) v0.3.6 fixes connector startup when an installation path contains spaces, including macOS Application Support paths.

Node.js 22.23.1 or later must still be available on the host PATH. Teaching behavior, account contracts, API-origin selection, and publisher metadata are unchanged.

This signed release is promoted to the stable channel and GitHub latest. Installing this version and restarting the provider are separate steps.

Assets include the signed manifest and its detached signature, the complete release archive, and the plugin-root archive. Release sequence: 9.

YipYap (Language) v0.3.5

YipYap (Language) v0.3.5

Signed sequence-8 release of the provider-neutral YipYap (Language) plugin.
This release changes publisher display metadata only: the author name in both
provider manifests and the owner and description of the public marketplace
catalogs now read MagneumCo, matching the organization that hosts the official
repository. No connector behavior, scope, callable, event kind, wire field,
teaching meaning, origin, credential binding, or updater pin changes.

Included

• publisher display name MagneumCo in the Claude and Codex plugin manifests
  and in the yipyap marketplace catalogs;
• the unchanged compiled future-production profile at
  https://api.magneum.co, the same five authenticated provider callables plus
  the explicit pairing bootstrap, and the same connector-interface packet;
• the unchanged updater pin MagneumCo/yipyap-language and the declared
  Node.js requirement of 22.23.1 or later.

Upgrade boundary

v0.3.4 installations may accept signed sequence 8 through the normal update
rules; v0.3.3 and earlier updaters still pin the previous repository location
and cross by a provider-native marketplace update or reinstall. Successful
apply 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.

Verification

The clean pushed source passes the repository validator and 306/306 tests
under Node 22.23.1 and under Node 26.5.0. Two independently sourced
signing-key copies produced byte-identical expanded trees, manifests,
detached signatures, deterministic archives, and plugin-root archives.

Not claimed

Publication does not prove provider activation, account connection, pairing,
Learning Mode, restart/new-root acceptance, migration of any installation,
rollback, provider-directory submission, or a public directory card.

YipYap (Language) v0.3.4

YipYap (Language) v0.3.4

Signed sequence-7 release of the provider-neutral YipYap (Language) plugin.
This release changes distribution identity and documentation only; connector
behavior, callables, scopes, event kinds, wire fields, and teaching meaning
are unchanged from v0.3.3.

Included

• the official public repository is now MagneumCo/yipyap-language; the
  updater's release pin, both provider manifests, the release allowlist, and
  the security policy name that location, and GitHub redirects the previous
  names;
• the declared Node.js requirement is >=22.23.1 with no upper major bound;
  the updater always enforced only that minimum, and the complete suite passes
  under 22.23.1 and 26.5.0;
• connector-first documentation: the hosted YipYap connector at
  https://api.magneum.co is the primary product surface for claude.ai, the
  Claude mobile app, and ChatGPT, and this plugin is the developer-host add-on
  for Claude Code and Codex, with provider-native marketplace install steps
  pinned to an immutable tag; and
• the same compiled future-production profile at https://api.magneum.co,
  the same five authenticated provider callables plus the explicit pairing
  bootstrap, and the same connector-interface packet.

Upgrade boundary

Immutable v0.3.3 installations keep their previous repository pin; GitHub
redirects it, and the v0.3.3 updater correctly rejects the moved asset URLs
in this release's signed index, so those installations move to v0.3.4 by a
provider-native marketplace update or reinstall from the new repository,
then a complete host restart and a new session. Nothing migrates silently and
no credential is copied, retagged, or reused.

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.

Verification

The exact source commit passes the repository validator and 306 of 306 tests
under Node 22.23.1 and under Node 26.5.0. Two independently sourced
signing-key copies produced byte-identical expanded trees, manifests,
detached signatures, deterministic archives, and plugin-root 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.

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.

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, and playback_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, and yip 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 brand YipYap.

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.

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.

Yip-Yap Language v0.2.0

Yip-Yap Language v0.2.0

Initial signed public distribution of the provider-neutral Yip-Yap Language
plugin for Claude and Codex.

Included

• one shared language-teaching Skill with thin provider manifests;
• a static, network-free lifecycle carrier for startup, clear, fork, resume,
  and compaction;
• the fixed five-call Yip-Yap connector bridge;
• read-first status, settings, and teaching-context rendering that fails closed
  to effective L0;
• signed stable-channel checking and inventory-verified candidate download;
• exact public release manifests, detached Ed25519 signatures, and deterministic
  archive verification.

Verification

The internal source validator and all 77 tests passed before candidate
generation. Two independently signed exports and deterministic archives must
be byte-identical before publication. The release page carries:

• yipyap-language-0.2.0.tar;
• manifest.json; and
• manifest.sig.

The public main branch carries the separately signed stable-channel pair at
release/latest.json and release/latest.sig.

Deliberate limits

This release does not claim provider installation, live account pairing,
Learning Mode activation, expanded-filesystem/provider apply, installed-host
smoke, rollback, ChatGPT support, or one-mixer cutover. The Yip Yap app owns
those installation and customer-state steps after publication. Every new
installation starts at L0, and activation requires a provider restart plus a
new root task.