docs: Add blog post about Conforma demo from Red Hat Summit 2026

[Acepresso]

Add blog post and resource entry for the Conforma demo presented at the Red Hat Summit 2026 event.

Co-Authored-By: Claude Sonnet 4.5
Ref: https://redhat.atlassian.net/browse/EC-1988

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: edb686c4-2b22-43b2-adee-4dd8c91f720d

📥 Commits

Reviewing files that changed from the base of the PR and between 9e972f2 and d29d5f2.

📒 Files selected for processing (1)

• website/content/resources/_index.md

Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review.

---

📝 Walkthrough

Walkthrough

Added a Red Hat Summit 2026 post and resource entry. The content describes SBOM-based license policy enforcement and links to the recording, slides, and demo repository.

Changes

Red Hat Summit license policy content

Layer / File(s)	Summary
Publish conference content website/content/posts/rh-summit-2026-license-policies.md, website/content/resources/_index.md	The site now includes Summit 2026 content about SBOM sources, Rego policy development, enforcement results, exceptions, validation examples, and demo materials.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: st3penta

Merge Risk: ⚪ Minimal · up to d29d5

This adds Summit 2026 conference content and related resource links with no current merge-readiness risk identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the documentation change and the Red Hat Summit 2026 Conforma demo.
Description check	✅ Passed	The description accurately states that the pull request adds a blog post and resource entry for the Red Hat Summit 2026 Conforma demo.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:34 AM UTC · Completed 8:57 AM UTC

Commit: 87c4a29 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $6.21

[github-actions]

🚀 Preview is available at https://3fbb3bee.enterprise-contract.pages.dev

[fullsend-ai-review]

Looks good to me

Previous run

Review

Findings

Low

• [content structure consistency] website/content/resources/_index.md:9 — The new resource entry omits the {{< rawhtml >}} embedded media block that most other resource entries include. However, this is consistent with existing precedent — the ‘How we use software provenance at Red Hat’ article entry also omits the rawhtml block because it links to an external article rather than an embeddable video. The Google Drive recording link is not straightforwardly embeddable via iframe the same way YouTube videos are.

• [commit-message-format] — AGENTS.md section 4 requires Conventional Commits format for commit/PR subjects. The PR title ‘Add blog post about Conforma demo from Red Hat Summit 2026’ lacks the required type prefix.
  Remediation: Update the PR title to use Conventional Commits format, e.g., docs: add blog post about Conforma demo from Red Hat Summit 2026.

Previous run (2)

Review

Findings

Low

• [structural-consistency] website/content/resources/_index.md:18 — Most existing resource entries include an embedded media block using the {{< rawhtml >}} shortcode. The new entry omits this. However, this is not universal (the "How we use software provenance" article entry also has no embed), and the recording is hosted on Google Drive which doesn't support standard iframe embedding. Consider adding an embed if the recording becomes available on YouTube.

• [structural-consistency] website/content/resources/_index.md:20 — Most existing resource entries use an introductory sentence followed by a bulleted list of topics covered. The new entry uses only prose paragraphs. Consider converting to the established format for consistency.

• [structural-consistency] website/content/posts/rh-summit-2026-license-policies.md:24 — The two most recent blog posts announcing resource entries end with a closing line encouraging readers to explore other resources (e.g., "While you're there, explore our collection..."). This new post ends immediately after the bold link.

• [commit-message-format] — AGENTS.md requires Conventional Commits format for PR titles. The current title "Add blog post about Conforma demo from Red Hat Summit 2026" does not use a type prefix (e.g., docs(website): add blog post about Conforma demo from Red Hat Summit 2026).

Previous run (3)

Review

Findings

Low

• [naming-conventions] website/content/posts/rh-summit-2026-license-policies.md:16 — Section heading 'Watch the demo' uses lowercase 'demo', inconsistent with the Title Case convention used in all other blog posts' section headings (e.g., 'Watch the Recording', 'Watch the Episode').
  Remediation: Change to ## Watch the Demo.

• [commit-format] — The PR title does not follow the Conventional Commits format required by AGENTS.md section 4. The title 'Add blog post about Conforma demo from Red Hat Summit 2026' is missing the type prefix.
  Remediation: Update the PR title to use Conventional Commits format, e.g. docs(website): add Red Hat Summit 2026 license policies blog post and resource entry.

[fullsend-ai-review]

🤖 Review · ❌ Terminated · Started 9:37 AM UTC · Ended 10:01 AM UTC

Commit: 87c4a29 · View workflow run →

[github-actions]

🚀 Preview is available at https://562dcb47.enterprise-contract.pages.dev

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 9:37 AM UTC · Completed 10:01 AM UTC

Commit: 87c4a29 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $6.10

[fullsend-ai-review]

🤖 Review · ❌ Terminated · Started 10:47 AM UTC · Ended 11:07 AM UTC

Commit: 87c4a29 · View workflow run →

[github-actions]

🚀 Preview is available at https://274f1dd4.enterprise-contract.pages.dev

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:47 AM UTC · Completed 11:07 AM UTC

Commit: 87c4a29 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $5.60

[simonbaird]

Looking for an embedded video player (assuming such a thing is possible for this video).

[github-actions]

🚀 Preview is available at https://bfb526ac.enterprise-contract.pages.dev

[github-actions]

🚀 Preview is available at https://fcc2dd53.enterprise-contract.pages.dev

[Acepresso]

Changes in the latest push:

• Embedded video in the resource entry
• Improved description in the resource entry
• All linked media (the slides and demo video) are publicly available

[github-actions]

🚀 Preview is available at https://8068b525.enterprise-contract.pages.dev

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 10:44 AM UTC · Ended 10:48 AM UTC

Commit: cd01138 · View workflow run →

[github-actions]

🚀 Preview is available at https://0070d82a.enterprise-contract.pages.dev

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 10:50 AM UTC · Ended 10:54 AM UTC

Commit: cd01138 · View workflow run →

[github-actions]

🚀 Preview is available at https://ec451346.enterprise-contract.pages.dev

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:56 AM UTC · Completed 11:06 AM UTC

Commit: cd01138 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $6.57

[robnester-rh]

LGTM

[simonbaird]

Lgtm.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 6:47 AM UTC · Completed 6:53 AM UTC

Commit: cd01138 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.03

[fullsend-ai-retro]

Retro summary for PR #548

A tiny docs-only PR (25 additions to a new blog post + 28 lines added to resources/_index.md) drew ~$24 of review compute across 4 successful review runs plus 2 concurrency-cancelled runs, using opus @ high each time. The workflow ultimately produced only low-severity style findings and one human-raised change request ("add an embedded video player").

Findings mapped to existing issues (skipped as duplicates)

• Docs-only PRs run full-firepower review. Already covered — no new proposal filed. See fullsend-ai/agents#301, #373, #497, #666, #879, fullsend-ai/fullsend#1900, #5298, #6891. New evidence: 25-line docs PR consumed $6.21 + $6.10 + $5.60 + $6.57 = $24.48 across 4 opus-high review runs; harness config harness/review.yaml @ v0.37.0 in fullsend-ai/agents hardcodes model: opus and effort: high with no content-aware sizing.
• Same commit reviewed 3× back-to-back. Commit 87c4a29 triggered 3 consecutive workflow_dispatch review runs within 2.5 hours (2026-08-25 08:34, 09:37, 10:47 UTC) with no intervening code change ($17.91 combined). Most likely explanation: each run's sticky bot comment first posted 🤖 Review · ❌ Terminated before updating to ✅ Success, prompting an operator re-dispatch. This is the exact manifestation described in fullsend-ai/fullsend#2619 ("Review status comment should not finalize until post-script completes"). New evidence: on this PR the transient-status bug plausibly cost 2× a full review ($12).
• Concurrency cancellations still burn 4–6 min of runtime. Runs 34467578635 and 34467985310 were cancelled via Canceling since a higher priority waiting request... after a fresh push, but still consumed 4–6 min of runner + partial model tokens each. Covered by fullsend-ai/fullsend#6991 and #7237.
• Review agent flagged missing Conventional Commits prefix on PR title. The reviewer surfaced this correctly, but there is no agent-driven fix path for a human-authored PR title, and repos configured for squash-merge can normalize the subject at merge time (which is what happened here — merged title became docs: Add blog post...). Related to fullsend-ai/agents#1114, #679, #819 but none of those address the re-flagging across successive reviews problem or squash-merge context — see Proposal 1 below.

Proposals filed (2)

1. Cross-run deduplication of unchanged low-severity findings on re-review (agents repo).
2. Document the resources-page embedded-video convention in the target repo's AGENTS.md so the review agent can enforce it at higher severity (source repo).

Agents repo discovered from run 32827244345 log: fullsend-ai/agents@v0.37.0 (commit dc7c805).

Proposals filed

• Document the resources page's embedded-video convention in AGENTS.md (in conforma/conforma.github.io)

Proposals skipped (target repo not allowed)

File manually or update create_issues.allow_targets in config.yaml:

• Review agent should suppress low-severity findings that were posted verbatim in the prior review sticky (fullsend-ai/agents)