docs: add evidence-bounded sprint demo agenda - #1992
Open
groupthinking wants to merge 2 commits into
Open
groupthinking wants to merge 2 commits into
groupthinking wants to merge 2 commits into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: groupthinking/EventRelay/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
documentation
Contributor
Dependency Review SummaryThe full dependency review summary was too large to display here (13153KB, limit is 1024KB). Please download the artifact named "dependency-review-summary" to view the complete report. |
groupthinking
marked this pull request as ready for review
September 18, 2026 20:57
Owner
Author
|
@copilot resolve the merge conflicts in this pull request |
groupthinking
enabled auto-merge
September 18, 2026 21:09
Contributor
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Pull request overview
Adds an internal sprint demo agenda document that clearly separates local/test-backed behavior from draft PR status and production-readiness claims.
Changes:
- Introduces a timed run sheet with expected outcomes, evidence links, and fallback steps.
- Adds an “evidence status” section that qualifies what can/can’t be claimed during the demo.
- Documents verification commands and known limitations/blockers for the walkthrough.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+11
to
+17
| | Area | Evidence | Qualification for the demo | | ||
| |---|---|---| | ||
| | Public Home-to-Studio handoff | [`HomePasteForm`](../apps/web/src/components/home/HomePasteForm.tsx), [`studio-handoff`](../apps/web/src/lib/studio-handoff.ts), and [`studio-handoff.test.ts`](../apps/web/src/lib/__tests__/studio-handoff.test.ts) | Demonstrate locally or describe through test evidence. The path validates a YouTube source, requests a Video Pack, and routes to `/studio?video=...`; no production result is implied. | | ||
| | Public Home sell surface | [`page.tsx`](../apps/web/src/app/page.tsx), [`home-sell-surface.test.ts`](../apps/web/src/lib/__tests__/home-sell-surface.test.ts), and [`landing-style-safety.test.ts`](../apps/web/src/lib/__tests__/landing-style-safety.test.ts) | Source and automated-test evidence from the current base branch. | | ||
| | Landing-page refinement | [Draft PR #1981](https://github.com/groupthinking/EventRelay/pull/1981) | Draft only. At preparation, `test-frontend` and `test` are successful, while `E2E Pipeline Tests`, `report`, and `Vercel` are failing. Do not present the refinement as reviewed, deployed, or production-ready. | | ||
| | Google sign-in retry | [Draft PR #1971](https://github.com/groupthinking/EventRelay/pull/1971) | Do **not** demonstrate. The PR is draft with no review decision, a failed Vercel check, a canceled report, and pending checks at preparation. | | ||
| | Production readiness | [`LAUNCH_CHECKLIST.md`](LAUNCH_CHECKLIST.md) and [`RUNBOOK.md`](guides/RUNBOOK.md) | These documents identify configuration and backend prerequisites; they do not prove that the demonstrated behavior is deployed. | |
Comment on lines
+21
to
+28
| | Minutes | Segment owner | Demo action | Expected visible result | Evidence | Fallback | | ||
| |---:|---|---|---|---|---| | ||
| | 0–2 | `Assign owner` | State the demo boundary and explain the UVAI YouTube URL-to-Studio goal. | The audience understands that the session is a local/test walkthrough, not a production launch or checkout demonstration. | This boundary; [`page.tsx`](../apps/web/src/app/page.tsx) | Read this opening statement and proceed to the evidence table. Do not make a live service claim. | | ||
| | 2–6 | `Assign owner` | In a local environment, enter the fixture URL `https://www.youtube.com/watch?v=auJzb1D-fag` on `/` and submit the public form. | The form builds a canonical YouTube watch URL, initiates the Video Pack request, and routes to `/studio?video=...`. | [`HomePasteForm`](../apps/web/src/components/home/HomePasteForm.tsx); [`studio-handoff`](../apps/web/src/lib/studio-handoff.ts); [`studio-handoff.test.ts`](../apps/web/src/lib/__tests__/studio-handoff.test.ts) | Show the focused test output and source links. Do not claim that an external backend analysis or deployment completed. | | ||
| | 6–8 | `Assign owner` | Enter a non-YouTube value in the same form. | The form keeps the visitor on Home and exposes the accessible message “Need a valid YouTube URL.”; no pack request should be initiated. | [`HomePasteForm`](../apps/web/src/components/home/HomePasteForm.tsx); [`studio-handoff.test.ts`](../apps/web/src/lib/__tests__/studio-handoff.test.ts) | Read the invalid-input test assertion. Do not bypass validation or invent a destination. | | ||
| | 8–10 | `Assign owner` | Review the evidence for the public Home surface and its boundaries. Do not invoke checkout. | The audience can see that Home is the sell surface and Studio is the workbench, with no claim of a guaranteed transcript or arbitrary-video production E2E behavior. | [`home-sell-surface.test.ts`](../apps/web/src/lib/__tests__/home-sell-surface.test.ts); [`landing-style-safety.test.ts`](../apps/web/src/lib/__tests__/landing-style-safety.test.ts) | Read the recorded focused test results. Keep billing controls visible only; do not begin a checkout session. | | ||
| | 10–12 | `Assign owner` | State the authentication resilience status. | No sign-in retry interaction is shown. The audience sees that it remains a draft, pending-review item with incomplete checks. | [Draft PR #1971](https://github.com/groupthinking/EventRelay/pull/1971) | Record “authentication retry deferred pending passing checks and review” as a blocker. Do not represent the feature as complete. | | ||
| | 12–15 | `Assign owner` | Close with current draft PR status, limitations, and required decisions. | The audience leaves with the exact distinction between local/test evidence, draft changes, and production readiness prerequisites. | [Draft PR #1981](https://github.com/groupthinking/EventRelay/pull/1981); [`LAUNCH_CHECKLIST.md`](LAUNCH_CHECKLIST.md); [`RUNBOOK.md`](guides/RUNBOOK.md) | End the walkthrough without deploying, publishing, modifying configuration, changing access, or charging a payment method. | |
Comment on lines
+50
to
+56
| | Item | Current status | Required handling | | ||
| |---|---|---| | ||
| | Landing-page refinement | [PR #1981](https://github.com/groupthinking/EventRelay/pull/1981) is an open draft with no review decision. Its `test-frontend` and `test` checks are successful, but `E2E Pipeline Tests`, `report`, and `Vercel` are failing. | Reference it as draft evidence only. Do not demonstrate it as reviewed or deployed. | | ||
| | Google sign-in retry | [PR #1971](https://github.com/groupthinking/EventRelay/pull/1971) is an open draft with no review decision, a failed Vercel check, a canceled report, and pending checks. | Omit the interaction. Record the work as deferred until review and verification are complete. | | ||
| | Vercel deployment evidence | The separate Vercel deployment integration can succeed while the `v0-uvai` Vercel check fails or is canceled. | Treat neither status by itself as proof of a production deployment. Do not deploy during this agenda. | | ||
| | Durable backend and production configuration | The launch checklist identifies environment, entitlement durability, provider, and backend prerequisites. The runbook describes local backend operation and troubleshooting. | Do not change configuration or start an external deployment as part of the demo. | | ||
| | Billing | The Home surface may display Workflow Pro information. | Keep checkout out of scope; do not create a checkout session, charge a card, or modify billing configuration. | |
| |---:|---|---|---|---|---| | ||
| | 0–2 | `Assign owner` | State the demo boundary and explain the UVAI YouTube URL-to-Studio goal. | The audience understands that the session is a local/test walkthrough, not a production launch or checkout demonstration. | This boundary; [`page.tsx`](../apps/web/src/app/page.tsx) | Read this opening statement and proceed to the evidence table. Do not make a live service claim. | | ||
| | 2–6 | `Assign owner` | In a local environment, enter the fixture URL `https://www.youtube.com/watch?v=auJzb1D-fag` on `/` and submit the public form. | The form builds a canonical YouTube watch URL, initiates the Video Pack request, and routes to `/studio?video=...`. | [`HomePasteForm`](../apps/web/src/components/home/HomePasteForm.tsx); [`studio-handoff`](../apps/web/src/lib/studio-handoff.ts); [`studio-handoff.test.ts`](../apps/web/src/lib/__tests__/studio-handoff.test.ts) | Show the focused test output and source links. Do not claim that an external backend analysis or deployment completed. | | ||
| | 6–8 | `Assign owner` | Enter a non-YouTube value in the same form. | The form keeps the visitor on Home and exposes the accessible message “Need a valid YouTube URL.”; no pack request should be initiated. | [`HomePasteForm`](../apps/web/src/components/home/HomePasteForm.tsx); [`studio-handoff.test.ts`](../apps/web/src/lib/__tests__/studio-handoff.test.ts) | Read the invalid-input test assertion. Do not bypass validation or invent a destination. | |
This was referenced Sep 18, 2026
# Conflicts: # docs/SPRINT_DEMO_AGENDA.md Co-authored-by: groupthinking <154503486+groupthinking@users.noreply.github.com>
auto-merge was automatically disabled
September 18, 2026 21:53
Head branch was pushed to by a user without write access
Contributor
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
This was referenced Sep 19, 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.
Canonical issue
Fixes #2040.
Also tracked as Notion “Confirm sprint demo agenda”.
Outcome
This pull request adds a concise internal sprint-demo agenda that distinguishes test-backed Home-to-Studio behavior from draft pull-request and production-readiness claims.
Scope
docs/SPRINT_DEMO_AGENDA.md, with a timed run sheet, owner placeholders, observable outcomes, fallbacks, evidence references, and verified limitations.Risk
0c020764c.Verification
studio-handoff.test.ts,home-sell-surface.test.ts, andlanding-style-safety.test.ts— 3 files and 23 tests passed.npm --workspace eventrelay-web run type-check.npm run build:web.git diff --check, repository reference existence check, and sensitive-data diff scan.Production evidence
Not applicable. This documentation-only change does not deploy, publish, initiate payment, modify production configuration, or change access.
Agent handoff