{{ message }}
Repository navigation
Conversation
<!-- Use a conventional commit-style title, such as "fix(hub): retain prototype history". --> ## Why <!-- Explain the problem and why this change matters in a short, plain-English paragraph. Link the issue when applicable. --> Agents asked to set up a prototyping repository have to assemble instructions from several guides. This makes local setup easy to confuse with full guidance authoring, team preparation, or Hub deployment, and decisions can get lost when moving to a fresh session. ## What changes <!-- Describe what becomes different for a first-time reader. Explain necessary terms. Include accurate Mermaid diagrams when they clarify the proposal, using before/after diagrams when helpful. Add screenshots for meaningful UI changes. --> <!-- Omit validation sections, checklists, and routine test/CI summaries such as "CI is green" or "tests passed". Mention only known verification gaps that affect the change, not disclaimers about drafting this description. --> Add a canonical prototype repository setup guide and link it from the README, agent instructions, and onboarding guides. It covers new and existing targets, a paste-ready fresh-session handoff, verifying the local starter, and continuing only to the requested outcome. The team setup path now explicitly prepares and shares the reviewed baseline before Hub setup. Installer and `/setup-skills` behavior stay unchanged. The cross-session workflow has been reviewed against the existing instructions but has not been exercised end to end in a fresh setup. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a303def4-749a-4a0e-9701-b7004ce1ef0e
Capture source when selecting a target and require a matching published Build before initial synchronization. Retain its identity across retries, follow-ups, and deletion. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because there is no eligible user to bill.
An enterprise owner can allow the organization to be billed for reviews like this by enabling Copilot code review for users without a license.
<!-- Use a conventional commit-style title, such as "fix(hub): retain prototype history". --> ## Why <!-- Explain the problem and why this change matters in a short, plain-English paragraph. Link the issue when applicable. --> Authors need to comment before publishing, including with uncommitted edits. Keeping that feedback on their device avoids storing unpublished comments in Hub or attaching them to the wrong Build. ## What changes <!-- Describe what becomes different for a first-time reader. Explain necessary terms. Include accurate Mermaid diagrams when they clarify the proposal, using before/after diagrams when helpful. Add screenshots for meaningful UI changes. --> <!-- Omit validation sections, checklists, and routine test/CI summaries such as "CI is green" or "tests passed". Mention only known verification gaps that affect the change, not disclaimers about drafting this description. --> The canvas saves unpublished comments privately on the author's device across restarts. Authors can edit or delete them. Source edits, commits and preview reloads preserve the target captured when selection starts. While open, the canvas uploads comments only when a newer imported Build matches their saved source. Confirmed uploads remove the local copy; failures retain it and show an error. Uncertain uploads are checked against Hub rather than blindly sent again. Published conversations keep their existing API and access rules, with no Hub draft records or migration. Local commenting requires a named branch with an initial commit. Source capture preserves staged files; active Git clean filters and changed submodules report an explicit limitation.  End-to-end publication against an authenticated Hub and full keyboard and screen-reader review remain unverified. Complete-suite runs also encountered intermittent canvas publication and checkout UI timeouts. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 1a0f3eb5-727a-4361-b09e-256fd982857d Copilot-Session: 81640dc7-0f59-4d95-9037-01b4eb681d03
Keep the live adapter and small presentation stories, replace cosmetic assertions with a functional renderer smoke, and minify the generated anchor validator through the existing Vite build. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Resolve overlapping local-review capture, Hub client renames, canvas selection and documentation changes. Rebuild generated bridge and renderer assets from the merged source. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
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
Unpublished Pick & polish improvements must remain on the author's device, even when the branch already has an older published Build. This completes the publication boundary for #42 and depends on the separate comment models and Build contract in #48. It follows the local-source capture approach in #37.
What changes
Starting target selection captures the local Git source without changing the real index. A new note can upload only after a successful published Build matches that captured source and was published after the note was saved. Later edits cannot replace the original capture. Capture failures and older notes without source information still allow local use, with an explicit explanation that they cannot synchronize.
The client saves the chosen Build identity before its first upload, so an uncertain result or restart cannot move the note to another Build. Follow-ups, status changes, and deletions retain that identity. Published improvements remain private to their author and separate from ordinary review comments.
The standalone Storybook prototype app is removed. Small stories use the real conversation component instead of recreating selection, storage and agent behavior. The packaged-renderer check now covers one functional flow rather than asserting colors, spacing and pixels; screenshots support human visual review. The generated anchor validator uses the same Vite minification settings as the existing preview bridge and Controls validator, while its TypeScript source stays readable.
This companion and #48 must land together; the new backend requires
build_numberon initial uploads.The retained live conversation and sidebar, captured through the packaged renderer with a local fixture preview and simulated agent answers: