docs: tighten sprint demo agenda with per-segment evidence gates - #2057
groupthinking with Copilot wants to merge 2 commits into
Conversation
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (3)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: groupthinking/EventRelay/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Co-authored-by: groupthinking <154503486+groupthinking@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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. |
Canonical issue
Outcome
This updates the internal sprint demo agenda to be explicitly evidence-gated per segment. Each time-box now maps owner + action + observable result + exact command + fallback script so presenters can distinguish verified evidence from narrative.
Scope
docs/SPRINT_DEMO_AGENDA.mdrun-of-show table into a 6-column format:Time,Owner,Demo action,Observable result,Evidence command,Fallback languageRisk
docs/SPRINT_DEMO_AGENDA.mdto prior revision.Verification
List exact automated and manual checks, tied to the current head SHA.
Production evidence
Not applicable. This PR is documentation-only and does not alter runtime paths or deployment behavior.
Agent handoff
Example excerpt