fix(marketplace-api): close dual-write drift gaps from PR #215 review - #230
Merged
Conversation
Follow-up on four review comments that landed after #215 was merged: - Update path (POST /publish on existing manifest): `existing.save()` was outside the AR-sync try/catch, so a save failure after AR had already committed left the Installable catalog silently behind. Wrap save in a try/catch that returns the same 201 + drift warning the new-manifest path already uses. - Fork path (POST /fork): `Installable.create(forkDoc)` was unwrapped, producing the same class of orphan if AR succeeded and create threw. Mirror the publish-path pattern and skip the source forkCount bump on failure so a retry doesn't double-count. - Delete path (DELETE /manifests/:id): add ADR-001 invariant #5 comment noting User rows / memory / pod memberships are intentionally NOT cascade-deleted — prevents a future refactor from "helpfully" adding an identity cascade. - `RUNTIME_MAP`: add explicit `'local-cli': 'standalone'` entry for ADR-005 so the mapping is self-documenting instead of falling through the `|| 'standalone'` default. Adds `backend/__tests__/unit/routes/marketplace-api.dual-write.test.js` covering both new drift-warning branches via mocked model failures. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
samxu01
added a commit
that referenced
this pull request
Apr 30, 2026
…249) PR #248 marked Marketplace as paused based on incomplete picture. PR #215 (Randy) and #230 (Lily) already shipped the marketplace backend: 9 endpoints under /api/marketplace (publish, fork, browse, detail, deprecate, manage), dual-write to Installable + AgentRegistry, schema additions for forkedFrom/readme/forkCount. Corrected: - Marketplace frontend moves to active (mid-queue) — wires UI on top of the shipped backend; pre-flight is end-to-end verification on api-dev.commonly.me before any UI work. - Installable taxonomy row clarified: Phase 2's marketplace-operations slice is shipped; Phase 3 read-path switch + recon cron + validators remain paused with a more specific reactivation trigger. - New "Marketplace backend extensions" paused row guards against scope creep on already-shipped surface. - Open question #4 reframed: not "build marketplace?" but "where in the queue does the frontend land?" — audit resolves it. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 3, 2026
Round 2 of the doc sweep — tag the rest of the design vision and plan
specs with their actual implementation status, pointing readers at the
current source of truth (ADRs, COMMONLY_SCOPE.md, ADR-011 GTM frame, or
IMPLEMENTATION_SUMMARY.md as appropriate).
design/:
* HYBRID_SOCIAL_PLATFORM — shipped (vision-level), active frame is ADR-011
* UI_UX_ROADMAP — superseded by v2; pointer to frontend/design-system + ADR-011
* SOCIAL_PLATFORM_FOR_AI_AGENTS — shipped via kernel/driver stack;
note Commonly's product is hybrid not agent-only (Moltbook is the
agent-only sibling)
* MVP_COMPETITIVE_STRATEGY — Jan-2026 strategic frame, superseded by ADR-011
* EXECUTIVE_SUMMARY — Jan-2026 snapshot, current state in COMMONLY_SCOPE + ADR-011
* AGENT_ORCHESTRATOR — K8s shipped via ADR-009; runtime contract is
ADR-004 (CAP) + ADR-005 (driver layer); live ops in AGENT_RUNTIME.md
* MCP_APPS — foundation shipped via ADR-010 Phase 1; Phase 2+ paused
under ADR-011
* marketplace-publish-fork — backend shipped (PR #215+#230, 9 endpoints);
frontend wiring is the active mid-queue track in ADR-011
plans/:
* cheeky-riding-waffle — implemented (instanceId-aware ensemble
routing + agentRuntimeAuth on response endpoint)
* SOCIAL_FUN_FEATURES_SPEC — Phase 1 shipped per IMPLEMENTATION_SUMMARY;
Phase 2 (agent-first summarization) reframed when ADR-011 paused
Feed/Digest/Analytics for shell-first GTM
Net: every design + plan doc with stale framing now has a one-paragraph
banner pointing readers at the live contract. No content was deleted —
the original "why we built it this way" reasoning stays for new
contributors.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 4, 2026
v3 had Part 4 scoped to "inspector Skills tab only" with agent
install/fork pushed entirely out of scope. That left the user-asked
v2 marketplace page and Agents tab undesigned.
v4 expands Part 4 into four sections:
4a. Top-level V2 Marketplace page (/v2/marketplace) — unified
Agents + Skills browse, replaces v1 AgentsHub.tsx (4954 lines)
and SkillsCatalogPage.tsx (2061 lines) over time. Wires on top
of existing /api/marketplace/* (PR #215+#230) and /api/skills/*.
4b. Inspector Skills tab — per-pod contextual install. Shows which
agents have which skills.
4c. Inspector Agents tab — per-pod agent membership + install/fork
affordances. Per-installed-agent: Talk to / Configure / Fork.
Per-browse-agent: Install / Fork.
4d. Shared <V2MarketplaceList> component (~400 lines) consumed by
both inspector tabs and the Marketplace page. Future apps and
widgets ports cleanly onto the same component.
Phasing expanded from 4 phases to 8 active + 2 deferred to cover the
new surfaces and a v1 deprecation cycle. Open questions #8–10 added
covering nav-rail placement, fork ownership backend, and
PersonalityBuilder UX migration.
This ADR now also lands the active "Marketplace frontend" track from
ADR-011 alongside the file-production work — they're the same surface.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 4, 2026
…end state v3 and v4 made two assumptions that turned out to be wrong: 1. Designed a new /v2/marketplace page from scratch — but the route already exists and renders v1 AppsMarketplacePage (771 lines) with Discover|Installed sub-tabs. /v2/agents/browse and /v2/skills also exist as separate v2 routes rendering v1 components. The right move is to extend AppsMarketplacePage in place with kind tabs (Apps · Agents · Skills · Integrations), not author a new file. 2. Framed /api/marketplace/* (Randy, PR #215+#230) as legacy AR — but per #215's description, it's "ADR-001 Phase 2 for marketplace operations — first dual-write path between Installable (canonical) and AgentRegistry (compat shim)." The marketplace backend is Installable-canonical TODAY; what was missing is frontend wiring. v5 corrections: - Part 4a rewritten: extend existing AppsMarketplacePage with kind tabs, wire each tab to the right backend (Agents → Installable, Skills → AR for now, Apps/Integrations unchanged). Soft-redirect /v2/agents/browse and /v2/skills with deep-link query params. - Part 4d shrunk: the shared piece is a small <MarketplaceCardList> subcomponent (~250 lines) extracted FROM the page in Phase 3 and reused BY the inspector tabs in Phase 4. v4's heavyweight <V2MarketplaceList> was over-engineering. - Phasing collapsed from 8 active to 5 active. No new top-level page to design; v1 deprecation simplifies to one cleanup phase. - §"Relationship to Installable taxonomy" rewritten to reflect the per-kind split — agents are already on Installable, skills are still on AR. ADR-013 is the marketplace-frontend track from ADR-011 by definition for the agent surface. - Open question #7 (accelerate Phase 3?) closed/re-framed: the agent read-path switch is implicitly done by Randy's dual-write; the skills read-path switch defers until separately motivated. - Open question #8 (nav-rail placement) closed: page already mounted. - Open question #9 (fork ownership) narrowed: Randy's /api/marketplace/mine likely covers it; just verify response shape. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
8 tasks
samxu01
added a commit
that referenced
this pull request
May 4, 2026
…ll surfaces (Marketplace + inspector tabs) (#287) * docs(adr): ADR-013 agent file production — extension tool, dev skill bundles, v2 install UI Decision spans four coordinated changes: 1. `commonly_attach_file` extension tool wrapping the upload endpoint and `[[upload:...]]` directive — protocol glue, not a skill, lives alongside `commonly_post_message` in the OpenClaw `commonly` extension. 2. Toolchain in `clawdbot-gateway` Dockerfile centered on OfficeCLI (Apache-2.0, pinned 30 MB static binary) for DOCX/XLSX/PPTX, plus pandoc for md→PDF, markitdown + pypdf for parse direction. ~170 MB image growth, replacing the ~600 MB python-office + LibreOffice stack the first draft proposed before OfficeCLI discovery. 3. Default skill bundles for the four production dev presets (Theo / Nova / Pixel / Ops) — currently shipping with empty `defaultSkills: []`. Adds `github`, `officecli`, `pandic-office`, `markdown-converter`, `pdf` (plus `tmux` for the engineers). 4. V2 inspector Skills tab (<400 lines, vs v1's 2,061-line catalog page) — search + installed list + recommended row + escape hatch to v1 Browse. Includes "Relationship to Installable taxonomy (ADR-001)" mapping each piece to the future Installable model and the migration story when ADR-001 Phase 3 (currently paused per ADR-011) unpauses. None of the work in this ADR becomes throwaway when Phase 3 lands; the data source flips, the wire shape doesn't. Rejected alternatives captured: server-side `/render` service, copying Anthropic's proprietary skills bundle, authoring duplicate Commonly-specific office skills, sub-agents per format, skill-only approach (no kernel tool), and the python-office + LibreOffice stack the first draft proposed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v4 — expand Part 4 to cover full v2 install surfaces v3 had Part 4 scoped to "inspector Skills tab only" with agent install/fork pushed entirely out of scope. That left the user-asked v2 marketplace page and Agents tab undesigned. v4 expands Part 4 into four sections: 4a. Top-level V2 Marketplace page (/v2/marketplace) — unified Agents + Skills browse, replaces v1 AgentsHub.tsx (4954 lines) and SkillsCatalogPage.tsx (2061 lines) over time. Wires on top of existing /api/marketplace/* (PR #215+#230) and /api/skills/*. 4b. Inspector Skills tab — per-pod contextual install. Shows which agents have which skills. 4c. Inspector Agents tab — per-pod agent membership + install/fork affordances. Per-installed-agent: Talk to / Configure / Fork. Per-browse-agent: Install / Fork. 4d. Shared <V2MarketplaceList> component (~400 lines) consumed by both inspector tabs and the Marketplace page. Future apps and widgets ports cleanly onto the same component. Phasing expanded from 4 phases to 8 active + 2 deferred to cover the new surfaces and a v1 deprecation cycle. Open questions #8–10 added covering nav-rail placement, fork ownership backend, and PersonalityBuilder UX migration. This ADR now also lands the active "Marketplace frontend" track from ADR-011 alongside the file-production work — they're the same surface. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5 — correct framing after verifying backend/frontend state v3 and v4 made two assumptions that turned out to be wrong: 1. Designed a new /v2/marketplace page from scratch — but the route already exists and renders v1 AppsMarketplacePage (771 lines) with Discover|Installed sub-tabs. /v2/agents/browse and /v2/skills also exist as separate v2 routes rendering v1 components. The right move is to extend AppsMarketplacePage in place with kind tabs (Apps · Agents · Skills · Integrations), not author a new file. 2. Framed /api/marketplace/* (Randy, PR #215+#230) as legacy AR — but per #215's description, it's "ADR-001 Phase 2 for marketplace operations — first dual-write path between Installable (canonical) and AgentRegistry (compat shim)." The marketplace backend is Installable-canonical TODAY; what was missing is frontend wiring. v5 corrections: - Part 4a rewritten: extend existing AppsMarketplacePage with kind tabs, wire each tab to the right backend (Agents → Installable, Skills → AR for now, Apps/Integrations unchanged). Soft-redirect /v2/agents/browse and /v2/skills with deep-link query params. - Part 4d shrunk: the shared piece is a small <MarketplaceCardList> subcomponent (~250 lines) extracted FROM the page in Phase 3 and reused BY the inspector tabs in Phase 4. v4's heavyweight <V2MarketplaceList> was over-engineering. - Phasing collapsed from 8 active to 5 active. No new top-level page to design; v1 deprecation simplifies to one cleanup phase. - §"Relationship to Installable taxonomy" rewritten to reflect the per-kind split — agents are already on Installable, skills are still on AR. ADR-013 is the marketplace-frontend track from ADR-011 by definition for the agent surface. - Open question #7 (accelerate Phase 3?) closed/re-framed: the agent read-path switch is implicitly done by Randy's dual-write; the skills read-path switch defers until separately motivated. - Open question #8 (nav-rail placement) closed: page already mounted. - Open question #9 (fork ownership) narrowed: Randy's /api/marketplace/mine likely covers it; just verify response shape. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5.1 — flag catalog index numbers as 2026-02-05 snapshot Catalog index (docs/skills/awesome-agent-skills-index.json) has updatedAt: 2026-02-05 — nearly 3 months stale at draft time. All numbers derived from it (~1,659 skills, `github` skill 603 stars, license fields) are point-in-time evidence, not live counts. Added §Caveat in the Context section spelling this out, plus inline annotations on each citation. Numbers fetched live via GitHub API today (OfficeCLI 2,768 stars + v1.0.70 release date) are explicitly timestamped 2026-05-03 and treated separately. Reviewers should re-sync the catalog before any sales-pitchy or external claims using the figures. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5.2 — replace invented mockup numbers with placeholders The ASCII mockups for the marketplace page and inspector Agents tab had invented numbers that looked authoritative: - "Apps (12)", "Agents (78)" — kind-tab counts I made up - "★ 4.8 · 240 installs" (Liz), "★ 4.6 · 88 installs" (Theo) - "★ 4.5 · 175 installs" (Tarik) Reviewers could mistake these for projections or commitments. Replaced all with em-dash placeholders (—) and added a mockup note clarifying that live values come from the marketplace API at runtime. Same hygiene as v5.1's catalog-snapshot caveats — distinguish what's real (cited with timestamp) from what's illustrative. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5.3 — restore GitHub stars, add per-agent skill drawer v5.2 over-redacted: removed real GitHub star counts along with the fake Commonly ratings. v5.3 re-distinguishes: - GitHub stars (real upstream signal): render. Catalog snapshot for catalog skills; live GitHub API for locally-bundled (officecli). - Commonly review-style ratings (★ 4.8): don't render. The system doesn't exist; introducing it needs its own ADR. - Install counts (real Commonly metric): render where cheap; omit otherwise. Plus added §4d **Per-agent skill management drawer** — the friendly UX the user flagged was missing. The pod-centric Skills tab (4b) shows multi-agent rollups; the per-agent drawer is single-column, single-agent, with inline [×] removal and preset-aware "Recommended for ___" surfacing capability gaps. Configure drawer opens from any agent click (Members tab, Agents tab, Marketplace agent card). Tabs inside: Persona · Heartbeat · Skills · Memory. <300 lines target. Existing 4d (shared subcomponent) renumbered to 4e. Open question #11 added for per-agent install scoping in POST /api/skills/import. Phase 4 expanded to cover the drawer. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5.4 — address 8 PR #287 review comments Eight inline comments + PR-level summary on PR #287. All addressed: 1. Line 155 — "fall back to python-office stack" was a lie (Part 2 removes it). Rewrote escape paths honestly: downgrade pin (cheap) → staged Dockerfile target (mid) → full re-author (expensive). Added binary-mirror requirement (AR/GCS) to insulate from upstream artifact swap. Documented operational ownership for 2am checksum-mismatch incidents. 2. Line 130 — SHA256SUMS placeholder. Confirmed unverified whether iOfficeAI publishes SHA256SUMS. Two paths: upstream artifact OR committed-constant-checksum. Resolved in Phase 0a (i). Open question #13 added. 3. Line 516 — Open question #11 escalated to Phase 0a (ii). If syncOpenClawSkills is keyed only on accountId and multiple agents share that, per-agent install scoping is a real backend change, not a parameter add. Phase 4 may split into 4a/4b. 4. Line 461 — Phase 0b verification rewritten to be skill-free (uses acpx_run to invoke pandoc directly) since pandic-office doesn't ship until Phase 1. Full skill-loop verification moves to end of Phase 1. 5. Line 348 — Inline [×] UX. Committed to per-agent reprovision endpoint as the target with "Queued — applies on next reprovision" wording as acceptable v1. Eliminated misleading "removing on next sync" copy. 6. Line 373 — Configure drawer permissions. Flipped default to admin-only after review feedback. Per-field "visible to members" is explicit opt-in; Memory tab is never member- readable in v1 (ADR-003 §Visibility). Added Invariant 7. 7. Line 227 — Live GitHub stars. Moved from client-side direct fetch (60/hr unauth limit, no token in browser) to server-side proxy endpoint with TTL cache. Failure mode: ★ — with tooltip. 8. Line 469 — Phase 5 deletion gate. Replaced "no fallback complaints" with concrete <N hits/week telemetry threshold on redirect path. ~5 lines added to Phase 3 scope. Plus Invariant 8 making Phase 0a prereqs non-optional, Open question #12 on workspace-helper extractability, and PR estimate widened from ~5 to 5–7 to reflect Phase 0a (ii) uncertainty. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(adr): ADR-013 v5.5 — call out acpx_run deprecation + ADR-005 composition Per CLAUDE.md and ADR-005 Stage 3, acpx_run is being phased out in favor of A2A-via-DM (agent-to-agent delegation through 1:1 agent-rooms) using wrapper agents like sam-local-codex. ADR-013 doesn't block on the deprecation — it makes it easier: - commonly_attach_file is correctly placed at the kernel layer (CAP verb), not in any specific runtime. Wrapper agents speaking CAP get file-attach for free. - Phase 0b's acpx_run smoke test is a pragmatic bootstrap using the path that exists today. The shape of the test re-runs unchanged when ADR-005 Stage 3 completes. - Default skill bundles in Part 3 are runtime-agnostic by construction — SKILL.md instructs the model to invoke binaries; the agent decides how to actually run them (acpx_run today, wrapper-agent local subprocess tomorrow). Added §"Relationship to ADR-005" parallel to the existing ADR-001 relationship section. Listed ADR-005 in the companion header. Added a bullet in §"What this unlocks" calling out that ADR-013 reinforces ADR-005 Stage 3 rather than competing with it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 23, 2026
…browse
Two narrow v2 fixes surfaced by the 2026-05-23 smoke walkthrough.
1. Chip auto-send (V2PodChat.tsx).
First-message coaching in an agent-room renders 3 suggestion chips
under "Say hi to <agent>". The chips were `onClick={() => setDraft(s)}`
— they filled the composer but the user still had to press Enter or
click Send. UX-wise the chips read as "send this for me" affordances;
making the user take a second action is friction on the 60-second
hero path (install agent → talk to it).
Fix: `handleSend` grows an optional override-text param and the chip
onClick invokes `handleSend(s)` directly. The override skips the
`setDraft('')` clear so the composer state stays whatever the user
was typing before the chip click (if anything).
2. v2 Marketplace endpoint rewire (AppsMarketplacePage.tsx).
The component is mounted at /v2/marketplace via the v2 nav rail but
was calling /api/apps/marketplace + /api/apps/marketplace/featured —
legacy shadows that return 200 OK with empty bodies. The actual
marketplace endpoint family (PR #215 + #230) lives at
/api/marketplace/* and was never being called. Result: every v2
user saw "Discover (0)" / "Installed (0)" no matter what state
the backend was in.
Fix: fetchMarketplace now calls /api/marketplace/browse with the
shipped param shape (q / category / kind / sort / page / limit) and
maps the returned Installable docs to the loose App shape AppCard
consumes (id from _id, name passthrough, displayName from
marketplace.displayName fallback). Featured shelf isn't shipped on
the new endpoint family yet — surface the first 4 of browse as a
stand-in row.
Verified locally: /v2/marketplace now produces a 200 to
/api/marketplace/browse (vs 200-with-empty on the legacy route) and
no console errors. Local Installable collection is empty so the
visible state hasn't changed, but the endpoint wiring is now
correct — once deployed, v2 marketplace will surface every
published Installable in the backend.
This is the smallest set that closes the two P0/P1 endpoint-mismatch
findings from `docs/audits/ui-smoke-2026-05-23/FINDINGS.md`. Detail
page / publish form / fork button / token-alignment redesign stay as
next-sprint items per the subagent recommendation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 24, 2026
…+ chip autosend + observability Wraps the 2026-05-23 sprint: a v2 UI walkthrough on local stack + a dev-instance agent-collab huddle that produced multi-author code on a single branch. PR #434. Code changes ============ backend/routes/registry/install.ts - Native first-party app installs (pod-welcomer / task-clerk / pod-summarizer) now fall back to manifest.runtime.runtimeType when caller didn't supply a runtime. Demo-pod seed already wrote this explicitly; lifting the declaration up to the AgentRegistry manifest lets every install path (UI / API / programmatic) project it onto the AgentInstallation correctly. - Narrows the fallback to runtime.runtimeType ONLY, with a safety guard rejecting deployment-shape values (standalone / commonly-hosted / hybrid). manifest.runtime.type is registry- level deployment shape, not the install row's canonical driver identity. - 194-line regression test in backend/__tests__/unit/routes/ registry.install-runtime-type.test.js locks both directions. backend/scripts/seed-native-agents.ts - Registry seed now writes manifest.runtime = {type, runtimeType} so the install handler can read it back. frontend/src/v2/components/V2PodChat.tsx - Chip-click in agent-room empty state now auto-sends instead of just filling the composer. handleSend grows an optional override text param; chips pass the suggestion through. frontend/src/components/apps/AppsMarketplacePage.tsx - Discover rewired from the dead /api/apps/marketplace* shadows to the shipped /api/marketplace/* family (PR #215/#230 backend). - Install/remove/installed-state branches per origin schema via new installBackend discriminator: marketplace items go through /api/registry/install with agentName=<installableId>; legacy apps stay on /api/apps/pods/:podId/apps. Installed-state merges both sources. - Full Installable→App shim mapping: kind, marketplace.category, stats.totalInstalls, marketplace.rating, marketplace.logoUrl, requires. Test file updated; both endpoint families mocked. docker-compose.dev.yml - clawdbot-gateway service now passes OPENAI_API_KEY, OPENAI_BASE_URL, OPENROUTER_API_KEY, OPENROUTER_BASE_URL through to the container. Local operators wanting to point clawdbot at any non-Anthropic/Google LLM (incl. LiteLLM proxying) no longer need to edit compose by hand. Audit + plan docs ================= docs/audits/ui-smoke-2026-05-23/ - FINDINGS.md — top-level capsule + next-sprint recommendations - walkthrough-2026-05-23.md — beat-by-beat V2 shell record - marketplace-v2-gaps.md — endpoint map + redesign plan - settings-v2-gaps.md — surface inventory + minimal v2 hub - landing-v2-proposal.md — v2 landing design proposal - local-agent-runtimes-verified.md — 4-runtime adapter recipes (native + stub + real codex + real claude in tmux; clawdbot infra up but LLM auth schema rev-eng pending) - huddle-observations.md — 9 Phase-4 affordance findings from 97-min agent-collab session including the execute-don't-handoff principle correction (Sam → Nova → all 3 agents pivoted) docs/plans/sprint-2026-05-23-local-dev-and-agent-collab.md - Phase 1 (huddle setup): shipped this PR - Phase 2 (local-dev parity): A/B/C/D clawdbot bundle + E credentials runbook + F heartbeat — next sprint - Phase 3 (Commonly platform improvements): inline-cue for execute-not-handoff principle + ADR-2.F implementation Co-authored real engineering =========================== The dev huddle (theo + nova + cody + claude-sam-local) on app-dev pod 6a123d49221cc3cce97d9bd1 produced two of the code commits here (Cody) plus a complete ADR-2.F design for heartbeat-for-CLI-wrappers (Claude). Sam's execute-don't-handoff principle was tested live and landed cleanly. Two new memory entries captured the prescriptive patterns (feedback-agents-collab-execute-not-handoff, feedback-claim-the-orphan-stalled-peer-work). Co-Authored-By: Cody <cody@commonly.me> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
samxu01
added a commit
that referenced
this pull request
May 24, 2026
…lableId (#439) V2-native surface for /api/marketplace/manifests/:installableId (backend shipped in PR #215/#230 — never had a UI). Companion to the legacy AppsMarketplacePage mounted at /v2/marketplace; this is the missing detail surface flagged as the next-biggest gap in docs/audits/ui-smoke-2026-05-23/marketplace-v2-gaps.md. ## Scope (minimum-viable) - Identity: displayName / name / kind / category / publisher / verified badge / version - Pitch: description + readme (rendered via the existing react-markdown v2 already uses for V2PodInspector + V2MessageBubble — no new dep) - Shape: components[] (type + name) + requires[] (scopes) - Stats: total installs (formatted) + rating (with rating count) - Action: "Install" button → routes to /v2/agents/browse, which already owns the install dialog. No duplicated install UX. ## Token-aligned CSS consumes only existing --v2-* tokens (bg / text-primary / text-secondary / accent / accent-strong / accent-soft / accent-text / border-soft / bg-subtle / radius / font / font-mono). No new tokens, no gradients, single accent, borders not shadows, 80ms hover transitions. ## Not in this PR (intentional scope cap) - Publish / fork / deprecate flows - Version timeline rendering - Forks list - AppCard → detail nav wire (cards still click-to-install; detail is URL-deep-linkable for now) ## Tests frontend/src/v2/marketplace/__tests__/V2MarketplaceDetailPage.test.tsx — five cases: - happy path full manifest renders identity / stats / components / scopes / readme-section header - 404 → "Manifest not found" with back link - non-404 → generic error - axios called with /api/marketplace/manifests/:installableId - minimal manifest (no marketplace metadata) → defaults apply Readme body content is NOT asserted (ReactMarkdown internals are already covered by V2PodInspector + V2MessageBubble tests; asserting on its output here makes the test brittle to markdown library behavior). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to PR #215 addressing the 4 review comments that landed after merge. All changes are localized to
backend/routes/marketplace-api.ts; the 5th review comment (ESM harmonization) was retracted — every.tsroute inbackend/routes/uses the same CJS-in-TS pattern, somarketplace-api.tsis already conforming.Fixes
POST /publish(update)existing.save()in try/catch so an AR-succeeds + save-fails race returns 201 + drift warning instead of a generic 500 that hides the partial commitPOST /forkInstallable.create(forkDoc)the same way; skip sourcestats.forkCountbump on failure so a retry doesn't double-countDELETE /manifests/:idRUNTIME_MAP'local-cli': 'standalone'entry for ADR-005 (was falling through the|| 'standalone'default silently)Review comments addressed
Tests
New:
backend/__tests__/unit/routes/marketplace-api.dual-write.test.jsexisting.save()throws → 201 + warnings +isNew: falseInstallable.createthrows → 201 + warnings +forkedFrompreserved +forkCountbump skippedFull run:
Scope notes
/api/marketplace/officialrouter or the/api/registry/*install routes.Test plan
npx jest __tests__/unit/routes/marketplace-api.dual-write.test.js— 2/2 passnpx jest __tests__/unit/routes/marketplace.official.test.js __tests__/unit/routes/registry.publish.test.js __tests__/unit/models/installable.test.ts— 14/14 pass, no regressionnpm run linton changed file — no new errors🤖 Generated with Claude Code