Repository navigation
Conversation
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.
What's added
chai/sprint-health,chai/release-health,chai/weekly-health-report: chai-bot coordinator skills for the weekly report of edge-context decision 0018 (no sub-agents, no prompts, team level only, missing data listed and never estimated).bin/chai_jira_adapter.py:query_jiratext → transform input, checked against real chai-bot output (fixtures are anonymized copies); key-ordered paging check (per project, since Jira'skey <is project-scoped); display-name roster match;get_jira_issuelink parser; feature spikes vialinkedIssues("<F>", "is blocked by");team-roster.mdparser (Rover email, "Not counted" excluded).bin/chai_report.py: mode, capacity (velocity × availability, else "not PTO-adjusted"; in release health the current sprint counts only its remaining working days), phase → section selection, Slack text. Unpointed work is a count, never an SP estimate (run-checks.py --no-hidden-scope-estimate); team-level actions go to the Scrum Master when edge-context names one.scrum_context.py/chai/scrum-context: per-sprint availability up to branch cut; "Not counted" members excluded. edge-scrum 1.6.0.Tests
516 pass (115 new) with
python3 -m pytest plugins/edge-scrum/bin/tests -q; markdownlint clean on the changed files.Dry run (2026-11-08, live Jira via mcp-atlassian, local only)
.roster.jsonbut not in edge-contextteam-roster.md. With the same roster the chai path matches exactly.fields, soextract_blocked_bycounts closed blockers andtransform-features.pyfinds no linked spikes; the midpoint analyzer also lists issues that are already done. The chai figures are correct; fix as a follow-up.Follow-up
plugins/edge-scrum/chai/).query_jirapages have not been seen yet; their handling is still an assumption.Summary by CodeRabbit