MemoStem plugin v0.6.3

What's Changed

• docs: add Cowork plugin directory submission guide by @OkYongChoi in #47
• chore: add skill sync for the ChatGPT web package by @OkYongChoi in #48
• chore: adopt the Recall Sprout logo in the public plugin by @OkYongChoi in #50
• docs: guide relation proposals when memo and flashcard are saved together by @OkYongChoi in #51
• docs(skill): lead with a worth-keeping rubric and move protocol detail to references by @OkYongChoi in #54
• docs(skill): keep one idea per card and titles within 60 characters by @OkYongChoi in #55
• docs(skill): make the takeaway card tie the main points into one conclusion by @OkYongChoi in #56
• chore: expect the guest shelf link refresh tool in the submission check by @OkYongChoi in #57
• chore: prepare 0.6.3 for the capture quality guidance by @OkYongChoi in #52
• feat: build the OpenAI portal ZIP from the memostem package by @OkYongChoi in #58

Full Changelog: v0.6.2...v0.6.3

MemoStem plugin v0.6.2

What's changed

• Renamed the public skill to memostem, covering getting started, explicit saves, consent-based suggestions, retrieval, draft review status, and recovery.
• Added the ChatGPT App plugin package and language-aware getting-started guidance.
• Expanded guest-shelf capture, link recovery, account transfer, and structured concept guidance.
• Refreshed ChatGPT submission prompts and review cases, and added a 62-second recording of guest save, shelf viewing, and preview without saving.
• Aligned package, marketplace, and MCP Registry metadata at version 0.6.2.

This release distributes the public plugin and remote-server metadata. ChatGPT directory review and approval are separate and are not completed by this release.

Full changelog: v0.6.1...v0.6.2

MemoStem plugin v0.6.1

Updates the public MemoStem skill so an explicit unnamed invocation keeps the existing capture flow, then falls back to recent conversation context only when the current conversation has no eligible candidate and the host actually provides that context. It reports unavailable context honestly and never transfers source transcripts.\n\nValidation: public plugin checks (44 tests), submission-readiness preflight, private MemoStem compatibility, and exact-main CI passed. Provider review and directory publication remain separate.

MemoStem plugin v0.5.3

What's Changed

• Complete OAuth capture for atomic memos and Q&A drafts by @OkYongChoi in #4
• Exclude developer skills from the MemoStem plugin by @OkYongChoi in #5
• Refresh MemoStem plugin branding and proactive capture copy by @OkYongChoi in #6

Full Changelog: v0.5.1...v0.5.3

MemoStem integrations v0.5.1

Registry publication compatibility patch for consent-first proactive capture.

• Keeps the v0.5.0 proactive-capture behavior unchanged.
• Shortens the MCP Registry description to its 100-character limit.
• Adds validation so future releases fail locally before publication.

MemoStem integrations v0.5.0

Consent-first proactive capture for MemoStem integrations.

• Supported AI clients can suggest one reusable result at a natural stopping point.
• A suggestion sends nothing and creation requires clear consent to the named material.
• Drafts remain private and pending until reviewed in MemoStem.
• Full transcripts, older conversations, secrets, and sensitive material remain excluded.

AI hosts control whether and when proactive MCP guidance is surfaced.

MemoStem integrations v0.4.0

MemoStem is now easier to discover and connect from ChatGPT, Claude, Codex, and other remote MCP clients.

Highlights:

• consumer-focused public repository and install guides
• clear explicit-selection, private-pending, human-review privacy boundary
• ChatGPT, Claude, and Codex listing metadata
• official remote MCP Registry metadata under io.github.girapphe/memostem
• GitHub OIDC publication workflow with a pinned publisher checksum
• paste-ready OpenAI and Anthropic review cases and submission fields

The application and MCP implementation remain private. OpenAI and Anthropic directory approval are separate provider review states.