docs(social-ops): record the first host integration and its trap - #33
Merged
Merged
Conversation
WHY: the capability layer's next-steps list said "Cuddler 侧接入" was still to do and floated an npm publish. Cuddler has since consumed the package (DiogenesModel/Cuddler#3482), and wiring it surfaced a packaging failure mode that any Next.js standalone host will hit — worth writing down here rather than leaving the next integrator to rediscover it in production. WHAT: - mark the Cuddler integration done; record that the lockfile pins a codeload tarball at a fixed commit, so a host image needs no git binary - document the two-glob output-file-tracing requirement: tracing only the .pnpm files ships the package unreachable, green everywhere locally and 503 on every call in production - bilibili/douyin/kuaishou stay endpointsVerified:false — the host deferred those developer applications, so nobody is verifying them soon - npm publish: deliberately not doing it; the git tarball already gives deterministic resolution and unpublish is restricted after 72h Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #32, now that the layer has a real consumer.
What changed
docs/SOCIAL_OPS_CAPABILITY_LAYER.md§8 anddocs/memory.md§3.8 both claimed the Cuddler integration was still ahead of us and floated an npm publish. Cuddler has since consumed the package (LuddiAI/Cuddler#3482), so this replaces the stale list with what actually happened plus the one thing worth warning the next integrator about.The trap, recorded
This package is CommonJS loaded through a runtime
require. Under Next.jsoutput: "standalone"a host must trace two paths — the real files undernode_modules/.pnpm/@influencex+social-ops@*/…and its ownnode_modules/@influencex/social-ops, the pnpm link that makes them resolvable.Tracing only the first ships all 30 files with none of them reachable. Local
vitest,tscandnext buildare all green; production answers 503 on every call. Cuddler added a CI policy suite to hold it.Also recorded
gitbinary — alpine bases have none.bilibili/douyin/kuaishoustayendpointsVerified: false. The host deferred those developer-platform applications (enterprise qualification plus per-capability review), so nobody will be verifying them soon. Do not quietly flip them.Docs only — no code, no tests affected.
🤖 Generated with Claude Code