01
What changed
This week (44 commits) surfaced extension bundles, the marketplace, and workspace sharing into the product, consolidated OpenAPI contracts as the single source of truth, and opened the first work on iOS authentication and a SwiftUI MVP. At the same time we strengthened large-repo skill installation and hardened boundaries around citations, OAuth, and session recovery to raise scalability and reliability.
- Added an installation layer for Agent Plugins v1–compatible bundles and .zip sources, implementing the extension lifecycle including versioning, update checks, reinstall, removal, and installability determination.
- Connected the admin-curated catalog to the marketplace.json index to enable search, localization, sync, and install flows, including support for Claude Code and Qwen-family marketplaces.
- Added workspace sharing/gallery and an Extensions management tab in Settings to view installed lists, component status, and bundle removal on a single screen.
- Established OpenAPI contracts as the Source of Truth and wired artifacts, contract tests, and CI drift gates; on iOS implemented refresh-body authentication, OAuth authorization-code exchange, and kicked off a SwiftUI MVP covering OpenMakeKit, chat, OAuth, and CI.
- Injected a tree limit into GitIngestService for large-repo skill installs, ensured concurrent creation of skill_manifests, and defaulted missing SKILL.md category fields to "general".
- Following 1.24.1, added tool-result evidence to the goal judge and prevented misuse of plan-zero completion; removed dead citation markers, enforced real-source-number constraints, strengthened OAuth account binding and search quotas, and added defenses against double-submits from Korean IME.
02
How this week was reconstructed
No matching local Claude Code project transcript was recovered for this period. This entry therefore describes only what the Git history can prove.
We audited the available Claude Code main sessions, their proven child lineages, and the repository history. Session notes explain intent and investigation; Git remains the authority for code that actually landed.
03
Team identity and project roles
OpenMake Team is the community identity; openmake_llm is the software project; OpenMake is the product name. Non-developer maker riskpw leads openmake_llm through vibe coding, and professional developer rocky supports its development.
Source evidence
OpenMake