Render Guide

PR titles, review and comment bodies, commit messages, branch names, repository names, session prompts, Jira issue summaries and statuses, transition from/to names, and Confluence page titles and space keys are free text, and on any shared repository other people author much of it. Before inserting any of it into the page, HTML-escape these five characters:

Escape & first so the other replacements are not double-escaped. For example, a PR titled Fix <input> focus & "Save" button renders as Fix <input> focus & "Save" button. Markup the recap adds itself (<code>, <strong>, <a class="pr-ref">) goes around escaped text, never inside it. Only use href values that are https://github.com/... URLs, or a Jira/Confluence url that begins with that source’s site_url over https. A Jira issue with a url of null renders its key as plain text, not a link.

The template’s Content-Security-Policy is a second line of defense: it lets only the page’s own script run and blocks outbound requests other than the brand fonts. Leave the <script> block and the policy untouched. The policy pins the script by hash, so an edited script stops running and the filters and Copy button break.

Placeholders

Self-explanatory: {{DATE}}, {{SUBTITLE}}, {{STAT_REPOS}}, {{STAT_SESSIONS}}, {{STAT_PRS_OPENED}}, {{STAT_PRS_APPROVED}}, {{STAT_GH_EVENTS}}, {{THEME_PARAGRAPHS}}, {{GENERATED_AT}}. {{DATE}} appears several times; replace every occurrence.

{{STAT_JIRA_ISSUES}} is the length of jira.issues; {{STAT_CONFLUENCE_PAGES}} is the length of confluence.pages. Each is — when its source is null (not collected), distinct from 0 (collected, nothing found). For a multi-day range, sum each day’s count, deduping by issue key for Jira and by page url for Confluence.

{{OPEN_THREADS}} is a plain-text, HTML-escaped summary of work still open at the end of the window: PRs from search.json/events.json that are still open (including drafts) and awaiting review or merge, branches from CreateEvent/PushEvent that have not been merged or deleted, streams whose status is open or deferred, and Jira issues from jira.issues whose status_category is not Done. Render each as a short phrase — pairing PR numbers with titles per the escaping rules above, quoting branch names in backticks, and pairing a Jira key with its summary — and join them with ; . Dedupe PRs by URL the same way streams do. Call out any Jira issue with returned: true as notable within its phrase (for example “sent back”), since it was moved backward in status within the window. When jira is null, omit the Jira issues entirely — never leave the whole placeholder empty solely because Jira is unavailable; fill it from the GitHub/session content alone.

{{PROJECT_CHIPS}}: one per project:

The script fills in the counts. {slug} must match the data-project value used on that project’s section and timeline events.

{{TODAY_BANNER}}: an empty string when step 1 did not gather today.json or it holds no events. Otherwise, built from those events:

Tags: New Repo, Sweep, Merged, Approval.

Standup card

The standup card sits at the top of the page, and its Copy button turns it into Slack-ready text. Fill these placeholders:

The Blockers heading is fixed in the template. {{STANDUP_PERIOD}} is Workday · {DATE} for a daily recap and Week · {DATE} for a weekly one.

RAG status

{{STANDUP_RAG}} is green, amber, or red. It colors the card’s border and status dot, and Copy emits it as :large_green_circle:, :large_orange_circle:, or :red_circle:. Derive it from in-window signals the collectors already emit:

• Jira issues with returned: true.
• Jira transitions in the window whose to is Blocked.
• Streams whose status is open or deferred.

Apply this heuristic:

• green: the period’s main work landed or moved forward, and no signal points to a setback. Open streams alone do not rule out green; unfinished work is normal.
• amber: the minimum whenever there is any blocker. Also amber when signals are mixed, for example one stream completed while another was deferred or an issue was sent back. When in doubt between green and amber, choose amber.
• red: a heavy or critical blocker load, such as several blocked items or a blocker that stops the period’s main work.

When jira is null, only the stream signal is available: derive the color from streams and session evidence alone, never treat the absent Jira signals as evidence of green, and say in the BLUF that Jira activity is not included.

The signals cover only the window, so work that is stuck with no activity inside it does not affect the color.

BLUF

{{STANDUP_BLUF}} is one HTML-escaped plain-text sentence summarizing the period: its main outcome and, when the status is not green, the reason. Copy takes the BLUF as text only, so it carries no links.

Sections

{{STANDUP_PAST}}, {{STANDUP_NEXT}}, and {{STANDUP_BLOCKERS}} are each a list of <li> elements:

• {{STANDUP_PAST}} (Yesterday or Last week): what the window delivered or moved forward. Merged PRs, issues moved to Done, substantive reviews, decisions, and Confluence pages with real content. Pick the most important items; fold routine work such as dependency bumps into one bullet or leave it out.
• {{STANDUP_NEXT}} (Today or This week): intended outcomes for the next period, drawn from open streams and returned issues.
• {{STANDUP_BLOCKERS}}: work stopped on something outside the user’s control, such as an issue moved to Blocked in the window or a session that ended waiting on another person or team. Say what each item waits on.

Bullets carry no status tokens such as `Done` or (PM-1, In QA); the link is the only reference. Leave a section with no items as an empty string, not a None bullet. The card shows its heading alone, and Copy prints - None under it.

Bullets

Lead with the problem solved or the value delivered, then the mechanism as a “by …” clause. Never open with a git verb (“Merged”, “Opened”, “Landed”) or a review-decision verb (“Approved”, “LGTM”, “Requested changes”); a review bullet names what was reviewed and what the feedback covered. Next bullets state an outcome (“Ship”, “Close”, “Resolve”, “Finalize”), never an activity (“Working on”, “Continuing”).

Put each Jira key or PR inside the sentence as <a class="pr-ref" href="..."> on the noun it refers to. The link text is the Jira key or owner/repo#N. No bare keys, and no references trailing the sentence or on a line of their own. The escaping and href rules above apply unchanged: escape the text first, use only GitHub URLs or Atlassian URLs that begin with site_url, and render a Jira key with a null url as plain text.

Copy turns each link into [text](url) and each <code> into backticks:

These rules apply only to the standup card and its Copy output. Stream cards and the timeline keep the <a class="pr-ref">#1234</a> plus title pattern below.

Stream card

Other bullet shapes, same <li> wrapper, escaped text per the rules above:

A Jira issue with a null url renders {KEY} as plain text instead of the link. Status semantics: completed means the work landed (PR merged, decision made, fix shipped). open means work in progress, not pushed or merged, or pending review. deferred means intentionally postponed. A Jira issue counts as completed when its status_category is Done, otherwise open.

Each Jira issue carries a returned boolean: true when one of its transitions in the window moved it backward (for example In Review → In Progress), false otherwise. When true, note it in the issue’s bullet in plain text (for example “(transitioned, In Review → In Progress, sent back)”), the same way involvement and transitions are already summarized there.

Search PRs merge into the existing PR bullets, deduped by PR URL, with no separate section or stat; a PR whose title or branch carries a matching Jira key shares a stream with that issue.

Project section

Timeline event

Show times in the user’s local timezone, matching the window’s timezone label. data-project lets the project chips filter the timeline; use the slug of the project the event belongs to.

Each Jira transition is one timeline event at its at timestamp, body {KEY} {from} → {to} (escaped), label Jira. Use class evt-merged/t-merged when to is a Done-category status, that is, the issue’s current status_category is Done and to equals the issue’s current status; otherwise use evt-review/t-review. No new CSS classes. Confluence pages carry no per-version timestamps, so they appear only in streams, never in the timeline.

Events after midnight but before the cutoff hour still belong to the recap’s workday. Insert this divider in the timeline before them: