Seed collaboration showcase fixtures - #183
Draft
HamptonMakes wants to merge 1 commit into
Draft
Conversation
The development seed stopped short of the newest features: nothing demonstrated agent attribution, comment threads, citation back matter, or the library audit trail, so demos and screenshots needed one-off scripts. Adds a collab-showcase document plus fixtures for each, following the existing deterministic, never-clobber-local-edits pattern. Co-Authored-By: Claude Opus 4.6 <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
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.
Why
The development seed stopped short of the features that landed over the last few weeks: nothing demonstrated agent attribution (#178/#181), comment threads in any state, citation back matter (#177), folder descriptions or the library audit trail (#176). Demos, screenshots, and manual testing all required hand-crafted one-off scripts — the "Claude (via Hampton)" screenshot for this week's #coplan update was staged exactly that way.
What
collab-showcasedocument ("Search latency: cutting p95 with a two-tier cache") exercising the reference system end-to-end: footnote citations with source links, explicit[§3](#section-3)numbered-section links, a tagged code fence, and prose the comment fixtures anchor toPlans::ReplaceContent— history renders "Claude (via …)" with fullapi_tokenprovenance, backed by a seeded root token carrying harness metadatatarget_plan, and one explicit curated repository referencerun_id, each audit event carrying agent name and token provenance)Risk Assessment
Low — development/test seed data only; no production code paths change. Fixtures follow the existing deterministic, never-clobber-local-edits pattern: anchors that no longer match after local edits skip with a warning instead of failing the seed.
References
Generated with Claude Code
Screenshots
The showcase document — citation superscripts, section links, comment highlights, TOC badges
Citation hover preview with source identity
References back matter — extracted citations, a resolved plan reference, and a curated repository
History with agent attribution