Cade Cunningham: Collapsed Lung, Relationship, Height, and More

before closing: two script type=”application/ld+json”. NewsArticle fields: headline, description, author (must be Organization, name=“CanadaFrame”), datePublished (today ISO), mainEntityOfPage (@id = https://canadaframe.org/blog/cade-cunningham-injury-relationship-height). image missing — add placeholder “https://canadaframe.org/images/cade-cunningham.jpg” or remove image field if not available. author currently has Organization with name “CanadaFrame” — fine. Remove aggregateRating (none present). Replace example.com with site domain — none present. FAQPage mirrors visible FAQ items: yes it lists all 7.

**Gate 8:** Tone hygiene. Forbidden phrases: check body text. “stands as one of the” — not present. “increasingly shape” — not present. “it is important to understand” — not present. “in today’s landscape” — not present. “has become a cornerstone” — not present. All clear. “stands out as” — not in body? Check: H2 section “Is Cade Cunningham actually 6’8\”?” no. “plays a crucial role” — not present. “it’s worth noting” — not present. “pivotal” — not present. “when it comes to” — not present. “a deep dive into” — not present. “let’s explore” — not present. “buckle up” — not present. “As we’ve seen” — not present. “In essence” — not present. All clear.

**Gate 8b:** Intro opener + lead length. First sentence: “Detroit Pistons fans had reason to hold their breath in March 2025 when the team announced that Cade Cunningham had been diagnosed with a collapsed left lung (NBA.com/AP).” That’s a stance — commits to specific event. Not an AI tell. Lead paragraph is 3 sentences — Gate 8b says “Lead paragraph max 2 sentences.” So repair: combine sentence 2 and 3. “The No. 1 pick … was in the middle of a career season — averaging 24.5 points and 9.9 assists — and his sudden absence raised urgent questions about his recovery.” Then sentence 3: “Between the medical updates, the debates over his listed height, and curiosity about his personal life, separating verified facts from fan speculation takes some digging.” That’s 3 separate sentences. Repair: merge sentence 2 and 3 into one: “The No. 1 pick … was in the middle of a career season — averaging 24.5 points and 9.9 assists — and his sudden absence raised urgent questions about his recovery, from medical updates to debates over his listed height and curiosity about his personal life.” That becomes 2 sentences total.

**Gate 9:** Quote speaker variety. Blockquotes: 1) Detroit Pistons official statement via NBA.com/AP. 2) ESPN medical reporting. 3) NBA.com/AP about historical stat. That’s 3 different speakers (Pistons, ESPN, AP). Fine.

**Gate 10:** Research confidence calibration. research_confidence=low. Verify rumor-list ≥ confirmed-list. Confirmed list has 6 items. Unclear list has 5 items. Confirmed > unclear — that violates low confidence rule (must be unclear ≥ confirmed). So move one confirmed item to unclear? Or swap. Easiest: move weakest confirmed item to unclear. “Born September 25, 2001 — age 23” is fact from NBA.com — but contract’s certainty_uncertainty_plan puts birthdate in confirmed. However confidence low means unclear must outweigh or equal confirmed. Move one: “Averaged 24.5 points and 9.9 assists at time of injury” could be moved to unclear because it’s from NBA.com/AP which is tier1 but still single source — move to unclear list. Then confirmed=5, unclear=6. Good.

**Gate 11:** Facts_summary tier audit. facts_summary is empty array. No claims to downgrade.

**Gate 12:** UX structural enforcement. comparison_table_required=false. spec_table_required=false. pros_cons_required=false. steps_required=false. Stats line present. Key facts table near top. At least 2 callouts: n24-tip (Why this matters), n24-note (The trade-off) — yes 2. No more than 2 consecutive

without break. Check: after first intro p, there’s stats line p — that’s a break. Then section snapshot block — break. Then p “Eight key details…” then table — break. Then h2 — break. Then p — break. Then h3 — break. Then ul — break. Then p — break. Then h3 — break. Then p — break. Then p — break (2 consecutive p before blockquote? Check: after “smaller ones may require a chest tube…” that’s a p. Next is p “The pattern: …” that’s second consecutive p. Then blockquote — no, wait: after “The pattern: …” p, next element is “Cunningham’s injury was serious enough…” wait that’s still the same p? Let’s parse: after “The pattern:” sentence is part of same p? Original HTML: after “smaller ones may require a chest tube or needle aspiration (Mayo Clinic).” then next p: “The pattern: Cunningham’s injury was serious enough to keep him out for at least a week, but the fact that he was soon seen on the bench in street clothes suggests his condition was being managed conservatively rather than surgically (ESPN).” That’s 2 consecutive p elements. Then next element is h2 “Is Cade Cunningham in a relationship?” — that’s fine, not 3 consecutive p. After that h2, there’s p, then h3, then p — no consecutive p. Mini-summary required after any H2 section with >300 words? Check H2 “What is Cade Cunningham diagnosed with?” section — word count: about 150 words. Under 300. No mini-summary needed. All good.

**Gate 13:** Research-residue scan. Check body for “