docs(handoff): rank 6 decided — the managed block names ONE docs URL, the repo list lives in the docs repo - #548
Merged
Merged
Conversation
…anaged block names ONE docs URL
ZacxDev
force-pushed
the
docs/handoff-rank6
branch
from
September 11, 2026 05:46
cf0753e to
bb61d87
Compare
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.
Updates the canonical agent-setup-onboarding handoff with this session's work on rank 6 (example apps).
The decision
The managed
AGENTS.mdblock gets one line pointing athttps://developer.civitai.com/apps/examples; the list of example-app repos lives in the docs repo. The rejected alternative — embedding seven repo URLs ininternal/cmd/templates/agents-app.md— loses because the block is written to disk in users' projects, so a literal that rots there cannot be recalled; only a re-run ofcivitai agent-setuprewrites it. A CI guard in this repo could only ever protect unshipped copies.Three premises in the previous handoff were wrong
All corrected by measurement, all recorded in the doc:
/apps/showcaseis the COMPONENT showcase (design tokens,TokenGallery.vue) — not an example-app gallery. The prior text conflated them. There was no example-app page at all;/apps/examples/404s.ZacxDev/, a personal account, not thecivitaiorg. An eighth,civitai/app-panorama-360, is org-owned and was missing from the list.topic:civitai-app-blockreturns 6 repos and a different set — two of the seven carry no topics at all.One of my own readings corrected
I measured
civitai.com/apps/run/<slug>→ 404 for all seven and nearly read it as "not published". The positive control killed it:civitai.com/appsitself 404s while/modelsreturns 200 — the whole route family is closed to an unauthenticated fetcher. The 404s are a fact about the route, not the apps.Work in flight (not in this PR)
Two branches are committed but unpushed, no PRs yet:
civitai/clifeat/agents-block-example-apps-link(c2c1b7f) — the template line, item 36's trigger widened (+1 byte, 30,442 → 30,443 against a 30,500 ceiling), decisions doc, and a new 256-line test that is unverified.civitai-developer-docsdocs/apps-examples-page(a2597fe) — the page,scripts/check-example-apps.mjsand its workflow. The guard's negative controls were incomplete.🔴 Ordering constraint recorded in the doc: the CLI PR must not merge before the docs page is live, since it ships a link that 404s today.