Release control center
#1136Muneerali199/Draftdeckai

fix: resolve 4 bugs in Draftdeckai

saurabhhhcodesfix/Draftdeckai-83373 → main commits18d agoopen on GitHub

15

risk score

Release decision

Review required

Review required. Trigger a Netlify preview build, re-analyze, then approve for production.

▸Risk score 15/100 — acceptable but non-trivial; route through a preview first.

▸Change touches user-facing flows — validate in a preview deployment before production.

▸A Netlify preview deployment will be triggered and a release report written to Notion.

Incident memory

How this change scores against your production history — 0 past incident(s) on the touched surface.

No incident history: Touched modules have no past incidents.

How Rakshak understands this change

AI reasoning layer · confidence MEDIUM · model Qwen/Qwen3-Next-80B-A3B-Thinking

fix: resolve 4 bugs in Draftdeckai (PR #1136) primarily changes api, components. It can affect api, components — 0 known dependency advisory(ies) and 0 matching historic incident(s) combine to drive its release score.

apicomponents

Failure hypotheses

▸Change to api (4 lines) touches a shared logic — downstream consumers may be affected without direct test coverage.

▸Change to components (4 lines) touches a shared logic — downstream consumers may be affected without direct test coverage.

Release risk score

Weighted from 9 evidence categories

15/ 100 release risk
criticalguardedclear

Blast radius

What this change can reach

Modules affected

2

api, components

Services reached

2

api, components

Estimated users exposed

active

active sessions

Changed files

4

8 lines of diff

Blast radius map

Severity-weighted dependency graph · active sessions

lowmediumhighcritical
apicomponentschange4 filesapilow50%componentslow50%2 modules · 2 services · reaches active sessions

Risk factors

Every point of the score is traceable to an observation

·

Traceability · No linked issue

low

No Jira issue is referenced from the PR description.

✓

Scope · Focused change set

low

4 files changed — contained diff.

✓

Incident history · No incident history

low

Touched modules have no past incidents.

✕

Blast radius · Multi-service impact

medium

Reaches 2 services.

✕

Test coverage · No tests in change

high

No test files added or updated for this change.

Affected modules

Coverage, incident history and change load per module

ModuleServiceFilesΔ linesCoverageIncidentsSeverity

api

api

api24—nonelow

components

components

components24—nonelow

Evidence chain

How Rakshak AI reached its decision

  1. GITHUB_INGESTPR #1136 ingested

    4 files, 8 lines changed by saurabhhhcodes → main

    ◆Aug 9, 07:05 AM

  2. JIRA_LINKNo linked issues

    PR description references no Jira issue — traceability is weak.

    ▲Aug 9, 07:05 AM

  3. NOTION_KNOWLEDGEProject knowledge loaded

    13 architecture notes · 2 incident records · 2 prior release reports consulted.

    ▣Aug 9, 07:05 AM

  4. IMPACT_MAPBlast radius mapped

    api (low) · components (low) — reaches active sessions.

    ◉Aug 9, 07:05 AM

  5. AI_REASONAI layer: how Rakshak understands the change

    fix: resolve 4 bugs in Draftdeckai (PR #1136) primarily changes api, components. It can affect api, components — 0 known dependency advisory(ies) and 0 matching historic incident(s) combine to drive its release score. • No prior incidents map to the exact changed file paths. • Blast radius spans 2 module(s) / 2 service(s), reaching up to active sessions.

    ◉Aug 9, 07:05 AM

  6. RISK_SCORERisk scored 15/100 — low

    Focused change set · 4 files changed — contained diff. — Multi-service impact · Reaches 2 services. — No incident history · Touched modules have no past incidents. — No tests in change · No test files added or updated for this change.

    ◉Aug 9, 07:05 AM

  7. DECISIONDecision: REVIEW

    Risk score 15/100 — acceptable but non-trivial; route through a preview first. Change touches user-facing flows — validate in a preview deployment before production. A Netlify preview deployment will be triggered and a release report written to Notion.

    ◉Aug 9, 07:05 AM

Change surface

4 files in the diff

app/api/proxy-image/route.ts+1-1
app/api/usage-dashboard/route.ts+2-0
components/diagram/diagram-preview.tsx+1-1
components/presentation/mobile-presentation-generator.tsx+1-1

Failure points

Where this change is most likely to break

No likely failure points identified.

Dependency security

CVE lookup on changed dependencies via osv.dev

No known advisories on changed dependencies

Missing coverage

Modules below the 60% test bar

No coverage gaps flagged

Agent trace

Swytchcode orchestration run

rakshak pipeline · run #9

01okgithub.github.fetch_pr

02okjira.jira.search

03oknotion.notion.knowledge

04okswytchcode.blast-radius

05okswytchcode.osv.scan

06okswytchcode.llm.reason

07okswytchcode.risk-engine

08okswytchcode.decision-engine

— decided review

Analyzed Aug 4, 09:15 AM · updated 18d ago