Repository navigation
DEV-2386: Regenerate the V3 agent indexes so Chat carries its V3 recipe - #328
Merged
Merged
Conversation
…et.Chat V3 recipe Generated artifacts still held the pre-PR #327 text saying V3 apps cannot use Fliplet.Chat. Regenerated with docs/bin/build-agent-indexes.mjs; no hand edits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Remove the emitters.mjs skip that hid Fliplet.Chat from v3/capabilities.md (its premise, that V3 apps cannot use Chat, no longer holds), flip its unit test, and regenerate. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying fliplet-cli with
|
| Latest commit: |
45d6e16
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9e4984d0.fliplet-cli.pages.dev |
| Branch Preview URL: | https://fix-dev-2386-v3-catalog-rege.fliplet-cli.pages.dev |
zeryabkhan91
approved these changes
Nov 16, 2026
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.
JIRA Issue
https://weboo.atlassian.net/browse/DEV-2386
Upstream half of QA defect FUNC-004 (NO-GO, 2026-11-12). Paired with fliplet-studio PR #9164 — this one must merge and publish first (see Sequencing).
Why this is needed
PR #327 corrected the frontmatter of
docs/API/fliplet-chat.mdto document the V3 path, but the generated artifacts were never rebuilt. So the published catalogue kept telling the V3 AI builder "V3 apps can't use Fliplet.Chat: build messaging on the app's own data sources". fliplet-studio refetches that published manifest at CI build time, so the stale text reached the builder fleet-wide and QA returned DEV-2386 NO-GO.Corroborating evidence that the artifacts were never regenerated together: the committed
llms-full.txtalready carried the Chat capabilities line (with the stale text) while the committedv3/capabilities.mddid not — the two were mutually inconsistent.Summary
.well-known/llms-v3-libraries.json,llms.txt,llms-full.txt,agent-skills/fliplet-js-api/SKILL.mdandagent-skills/index.jsonfrom the existing frontmatter withnpm run build:agent-indexes. No file was hand-edited.docs/bin/emitters.mjsthat skippedAPI/fliplet-chat.mdwhen emittingv3/capabilities.md. Chat now appears under## Communications, so the published index of "every JS API surface available to V3 apps" finally includes it.The exclusion came from
080f5b7a"Exclude V2 Chat from generated V3 capabilities" (2026-11-03) and its test24b35c42, made under the pre-DEV-2386 assumption that V3 apps cannot useFliplet.Chat. That premise no longer holds: PR #327 documented the V3connect({ dataSourceId })+login({})path.One consequence worth knowing: with the code-level skip gone,
v3/capabilities.mdis derived purely from frontmatter, so the only supported way to exclude a doc isexclude_from_v3_catalog: truein its frontmatter. That is the right direction — it makesdocs/CLAUDE.md:306-311's claim that the page "cannot drift" true for the first time — but it does remove the escape hatch that commit used.Chat entry, before → after
"Chat API for V2 apps with a Chat component. Not available to V3 apps: build messaging on the app's own data sources."→ "Chat API for one-to-one chats, group chats and public channels. V2 apps use a Chat component; V3 apps connect with a login data source.""V3 apps can't use Fliplet.Chat: its server routes need a Chat component on a screen…"→ "V3 apps: call Fliplet.Chat.connect({ dataSourceId }) with a data source that has a login, then await chat.login({})… Message encryption is not access control."Testing
npm run test:unit: 228/228 passingnpm run check:docs(--strict): exit 0generatedAttimestampfliplet-chat(index 4) differs; no unrelated catalogue churndocs/API/fliplet-chat.mdfrontmatter.well-known,v3andbin: 0 hitsTesting notes
Risk Assessment
Sequencing
This must be merged and published to developers.fliplet.com before fliplet-studio PR #9164 reaches a staging build, because Studio's
prebuildrefetches this manifest and overwrites its committed copy. After deploying, confirm by runningnpm run fetch-fliplet-apisin fliplet-studio and checking the diff is empty — do not infer publication from the merge.Known gap, deferred by decision: DEV-2778
Nothing in CI compares the generated artifacts against the doc frontmatter, which is exactly how this defect shipped. A guard was built and then removed from this branch because it carried its own problems (its
pathsfilter did not cover the generated files, and it would have obliged every docs author to commit regenerated artifacts whileCONTRIBUTING.mdsays the opposite). It is tracked with the full diagnosis in DEV-2778. Until that ships, a doc edit can still land without regenerated artifacts.🤖 Generated with Claude Code