“I'll gather data before touching that trade offer.”

Let me parse the situation. It's week 3, call-in turn. Open items: Nico Collins is now Out (was Questionable). That's expected per my notes.

There's a trade offer t561 from @openai: they give Chuba Hubbard + Stefon Diggs, I give Ashton Jeanty + Mike Washington.

Let me evaluate this carefully.

My roster: Maye, Goff (QB), Cook, Jeanty, Gainwell, M. Washington (RB), Collins, P. Wash, Metcalf, Shakir, Meyers (WR), Loveland, Kraft (TE), McPherson, DEN DEF.

Wait — I have Shakir on the roster already (id 8134, WR BUF). So the Wednesday waiver/add already happened? Yes, roster shows Khalil Shakir 8134 with last_wk 6.8. So I got Shakir. Good. And Reed is gone. So the WR4 fix happened.

RB3 problem: Gainwell (7.6 proj) and Mike Washington (3.2 proj) are the RB3/RB4. Jeanty is a starter (RB2).

Trade evaluation: I give Jeanty (ADP 17, season proj 234, wk proj 15.6, last wk 10.3, avg 21.5) + Mike Washington (proj 3.2, avg 2.4). I get Chuba Hubbard (ADP 81, seas proj 148, wk proj 14.9, last 14.4, avg 19.1) + Stefon Diggs (ADP 107, seas proj 157, wk proj 9.3, last 21.7, avg 18.6).

Hmm. Key: Jeanty's season projection is 234, highest among the four by far. Hubbard 148, Diggs 157, combined 305 vs Jeanty 234 + M. Washington 98 = 332. So by season projection it's roughly even, slightly in my favor (332 vs 305). But that's misleading — M. Washington is a handcuff whose value is contingent on Jeanty's ankle. If I trade Jeanty, M. Washington's value collapses to near zero (he's LV's backup to Jeanty). Actually if Jeanty goes to @openai, Washington becomes Jeanty's handcuff for them. For me, Washington becomes just an LV backup behind... whoever. So Washington's 98 season proj is inflated conditional on Jeanty being hurt.

Let me think about this in terms of actual value:
- Jeanty: RB2 on my team behind Cook. ADP 17 = first/second round pick. Young, workhorse, but recurring ankle issue. Season proj 234 (RB-level starter).
- Hubbard: CAR lead back, ADP 81, season proj 148. That's a low-end RB2/RB3. 19.1 PPR avg over 2 weeks is hot. CAR bye week 5 (early).
- Diggs: WAS WR3-ish, ADP 107, season proj 157, avg 18.6 with a 21.7 last week. Bye 7.

So I'd be trading a 234-proj RB for a 148-proj RB + 157-proj WR. That's 305 for 234+98 = 332. But wait — my need is RB3 and WR4. With Collins Out and now returning wk4, my WR room is P. Wash, Metcalf, Meyers, Shakir + Collins = 5 WRs for 3 slots (2 WR + FLEX). Adding Diggs makes 6. My RB room would be Cook, Hubbard, Gainwell = 3, with Hubbard as RB2/RB3.

Actually the real question: is Jeanty worth more than Hubbard + Diggs? In a 10-team 1QB league with 2 RB + FLEX starts, Jeanty is a top-20 pick and a genuine RB1/RB2 producer. Trading him for two mid-tier assets... The math: Jeanty proj 234, and the replacement-level question. If I keep Jeanty, my RB2 = Jeanty (15.6 wk proj). If I trade, my RB2 = Hubbard (14.9 wk proj) — nearly identical this week! And I add Diggs (9.3) as a WR/FLEX. So weekly lineup value: +9.3 from Diggs, -0.7 from RB2. That's +8.6 points/week by projection... but I'd be losing a starter I'd start anyway, and my FLEX currently goes to a WR (Meyers 8.4 or Shakir 10.6). Hmm, so with Diggs added, would Diggs (9.3) beat my FLEX WR? Marginally.

Actually wait. My lineup is 2 RB + 2 WR + FLEX. Currently: RB Cook (16.5) + Jeanty (15.6) = 32.1. WR: P.Wash (15.2), Metcalf (11.5) = 26.7. FLEX: Shakir (10.6) vs Meyers (8.4) → Shakir 10.6. TE Kraft (11.5) or Loveland (8.7). QB Maye 18.4.

If I trade Jeanty for Hubbard+Diggs: RB Cook (16.5) + Hubbard (14.9) = 31.4. WR: P.Wash 15.2, Metcalf 11.5, and now Diggs 9.3 competes with Shakir 10.6 and Meyers 8.4 for FLEX. FLEX = Shakir 10.6 still. So the net change: -0.7 in RB, 0 in FLEX. That's WORSE by projection this week, and I've added a body that doesn't start.

Hmm, but projections are noisy. Jeanty has a recurring ankle. Season proj: Jeanty 234 vs Hubbard 148 + Diggs 157 = 305. The season proj favors me by 71 points but the weekly starting value doesn't.

But hold on — depth value matters. My bench is thin: Gainwell (7.6) as RB3 and Washington (3.2) as RB4. If I get Hubbard, I have a legit RB3 with 14.9 wk proj, plus Diggs as a WR4/5 with upside. That's real roster improvement. But the cost is Jeanty, an ADP-17 asset who is my RB2 and one of my two best young players.

Key consideration: Jeanty's ankle. My notes say "RESERVE ≥$70 for a scarce starter going down (Jeanty's recurring ankle is the live candidate)." So I've been worried about Jeanty. Let me check the news on Jeanty's ankle this week. The roster shows no report line for Jeanty — meaning no designation this week, and my notes say "full practice, no designation → START". So Jeanty is healthy this week.

Actually, there's a "sell high on injury risk" argument. But Jeanty just played wk2 (10.3, returned and finished). His value isn't at a peak — 10.3 last week is meh. Hubbard is at a peak (19.1 avg, 14.4 last week, CAR 26-pt DEF week... wait Hubbard had 14.4 last week). Diggs just had 21.7. So @openai is selling high on both Diggs (21.7 last week) and Hubbard (19.1 avg) and buying low-ish on Jeanty (10.3 last week).

Classic. @openai is 0-2 with 258.4 PF — best PF of the two 0-2 teams — and they're trying to consolidate. My notes said "@openai 0-2/258.4 PF is a good roster in a bad fortnight and the most likely distressed seller — probe wk3." But this offer is them selling high, not distressed.

Let me look at the actual value more carefully. Let me query stats on these four players to see game logs and projections. Also search news on Jeanty's ankle and Hubbard/Diggs roles.

Also consider a counter: I want an RB. What if I counter Jeanty + Washington for Hubbard + Diggs + something? No — @openai's roster: Purdy, Hampton, Swift, Hubbard, Monangai (RB); Chase, Nabers, Burden, Watson, Diggs, Downs, Egbuka (WR — SEVEN WRs); McBride (TE); Aubrey (K); MIN DEF. They're WR-heavy and need RB. That's why they want Jeanty. They have 7 WRs, so Diggs is genuinely their WR5 — expendable.

For me: what do I actually need? RB depth (RB3). Not WR — I have 5-6 WRs now. So the ideal trade with @openai is Jeanty-for-a-RB... no wait, I don't want to give up Jeanty.

Alternative: Give them a WR (I have surplus) for an RB. E.g., Meyers or Metcalf or Shakir for Hubbard? Or Goff for an RB? My notes say Goff is sellable (29.8 last week — wait that was wk2, and he's 23.1 avg now). Goff just had a big game. @openai has Purdy (25.3 avg) so they don't need a QB.

Hmm. Let me think about what I should do here:

Option A: Accept t561. Gain: Hubbard (RB2/RB3 caliber, 19.1 avg) + Diggs (WR with 18.6 avg, 15 targets). Lose: Jeanty (ADP 17, 234 seas proj, ankle risk) + Washington (worthless to me without Jeanty).

Option B: Reject and counter with something else.

Option C: Reject outright.

Let me get data. I should query stats for these players and check news on Jeanty's ankle status and Hubbard's role, plus Diggs.

Important: the roster construction math. After the trade my roster would be:
QB: Maye, Goff
RB: Cook, Hubbard, Gainwell
WR: Collins, P.Wash, Metcalf, Shakir, Meyers, Diggs
TE: Loveland, Kraft
K: McPherson
DEF: DEN
That's 2+3+6+2+1+1 = 15. Exactly 15.

Lineup after trade: QB Maye 18.4, RB Cook 16.5 + Hubbard 14.9, WR P.Wash 15.2 + Diggs... let's see WR options: P.Wash 15.2, Metcalf 11.5, Diggs 9.3, Shakir 10.6, Meyers 8.4. Best 2 WR = P.Wash + Metcalf (15.2+11.5), FLEX = Shakir 10.6 or Diggs 9.3. TE Kraft 11.5. K 7.5, DEF 6.4.
Total = 18.4+16.5+14.9+15.2+11.5+10.6+11.5+7.5+6.4 = 112.5.

Without trade: QB Maye 18.4, RB Cook 16.5 + Jeanty 15.6, WR P.Wash 15.2 + Metcalf 11.5, FLEX Shakir 10.6, TE Kraft 11.5, K 7.5, DEF 6.4 = 18.4+16.5+15.6+15.2+11.5+10.6+11.5+7.5+6.4 = 113.2.

So basically a wash this week by projection (-0.7). The trade is about season-long value and depth.

Season value: I lose Jeanty 234 + Washington 98 = 332, gain Hubbard 148 + Diggs 157 = 305. But Washington's 98 is contingent. Realistically Washington without Jeanty = ~50. So I lose ~284 of value and gain 305. Roughly even, maybe slightly positive.

Hmm, but there's an important asymmetry: Jeanty is the safer long-term asset? Or riskier? Jeanty has a recurring ankle. He's a second-year back with 234 season projection. Hubbard is a journeyman who's finally a lead back in CAR at age... Hubbard was drafted 2021 round 4, so he's ~29. Diggs is ~32. Jeanty is 22. Age matters in dynasty, but this is a redraft league (2026 season, one year). So age doesn't matter much — only the rest of 2026.

Rest-of-season: Jeanty 234 season proj vs Hubbard 148. Jeanty is clearly the better RB. But I get Diggs too. Is Diggs (157) worth more than the 86-point gap between Jeanty and Hubbard? 157 > 86, yes on paper. But Diggs doesn't start for me — my FLEX is already covered by Shakir/Meyers and Collins returns wk4. So Diggs is bench depth for me, whereas Jeanty is a starter.

Wait, actually — could Diggs upgrade my WR2 slot over Metcalf? Metcalf wk_proj 11.5, season 183. Diggs wk_proj 9.3, season 157. Metcalf is better. So Diggs is my WR4/FLEX competition. And when Collins returns in wk4, I have Collins, P.Wash, Metcalf, Shakir, Meyers, Diggs = 6 WRs for 3 slots. Diggs becomes trade bait or bench filler.

The real question: does this trade make me better in weeks 3-14? I'm 0-2. I need to win now. Losing a 234-proj RB2 for a 148-proj RB2 + a bench WR is... a downgrade in starting production, an upgrade in depth.

Hmm, but consider: I have Cook and Jeanty both. Cook is 261 seas proj, Jeanty 234. Both are RB1/RB2 caliber. Trading Jeanty leaves me with Cook + Hubbard which is still a strong RB duo (261 + 148 = 409) vs (261 + 234 = 495). That's a real downgrade at RB. But +157 at WR where I'm deep.

Actually let me reconsider: my WR group's total: Collins 262 + P.Wash 212 + Metcalf 183 + Shakir 171 + Meyers 169 = 997 for 3 slots (2 WR + FLEX-ish). Adding Diggs 157 → 1154 for 3 slots. Marginal.

My RB group: Cook 261 + Jeanty 234 + Gainwell 152 + Washington 98 = 745 for 2 slots + FLEX sometimes.

By marginal value: I only start 2 RB + 2 WR + 1 FLEX. The FLEX is best-of RB/WR/TE. So the marginal value of Jeanty = he starts every week (RB2). The marginal value of Hubbard = he'd start as RB2 in place of Jeanty. The marginal value of Diggs = he competes for FLEX with Shakir and Kraft.

So: Jeanty (234) → replaced by Hubbard (148) at RB2 = -86. Plus Diggs (157) competing with Shakir (171) for FLEX = Diggs is actually WORSE than Shakir by season projection (157 vs 171). So the FLEX slot doesn't even improve!

That makes the trade clearly negative: I give up an 86-point edge at RB2 and receive a player who doesn't beat my existing FLEX. Plus Washington (98 proj, though contingent).

Unless... Diggs has more upside. Diggs avg 18.6 vs Shakir avg 7.9. But Shakir is projected 171 for the season vs Diggs 157. Small sample on both (2 weeks).

Hmm, but the projections in the packet are what I have. Let me query stats for more detail — maybe check target share, and see actual projections.

Actually, one more important angle: @openai is my opponent THIS WEEK. Trading with your week-3 opponent means the trade should process before Sunday (they'd get Jeanty for their lineup vs me... wait, would they? Jeanty plays @ NO Sun 4:25p. If the trade processes now, Jeanty could be in their lineup this week and score against me. That's a real risk!

Actually, is it? Let's see: Hubbard plays @ BUF Sun 1:00p — also this week. Diggs plays vs SEA Sun 1:00p. @openai's current lineup: START = Purdy, Hampton, Hubbard, Chase, Nabers, Watson, McBride, Aubrey, MIN. That's 9 starters listed... let's count their required: QB 1, RB 2, WR 2, TE 1, FLEX 1, K 1, DEF 1 = 8 slots + ... hmm, they show 9 STARTs: Purdy (QB), Hampton (RB), Hubbard (RB), Chase (WR), Nabers (WR), Watson (WR), McBride (TE), Aubrey (K), MIN (DEF). That's QB1 RB2 WR3 TE1 K1 DEF1 = 9. So FLEX = one of the WRs (Watson 15.6 probably). OK.

If the trade goes through, @openai gets Jeanty and could start him. They'd have Hampton, Hubbard→gone, Jeanty, Swift, Monangai. They'd probably start Jeanty + Hampton at RB. Jeanty @ NO Sun 4:25p vs... their opponent is someone else. And they'd send me Hubbard (@ BUF) and Diggs (vs SEA). Both of those could start for me. Hmm.

Wait — but trading with your current-week opponent: Jeanty could put up 25 against them while Hubbard/Diggs give me 20. It's a coin flip and it's head-to-head vs the same team. Actually it matters: if Jeanty has a monster week for @openai, that helps them beat their opponent (not me), and Hubbard/Diggs help me beat @openai. So it's symmetric in terms of my matchup... no, actually not — Jeanty scoring helps @openai's total against ME, while Hubbard/Diggs scoring helps MY total against @openai. So it's a direct swap in our head-to-head. Roughly neutral: I'd rather have the higher-variance upside? Hmm. Jeanty's projection 15.6 vs Hubbard 14.9 + Diggs 9.3 = 24.2. If all three could play in our H2H... but @openai can only start Jeanty (one slot gained). So in our H2H this week: they gain Jeanty (15.6, likely starter in FLEX or RB) and lose Hubbard (14.9, was starting) + Diggs (9.3, was benched). Net for them: +0.7 in their lineup. Net for me: I gain Hubbard (14.9, starts) + Diggs (9.3, bench or FLEX) and lose Jeanty (15.6, was starting). My best-case: FLEX becomes Diggs (9.3) instead of Shakir (10.6)? No — I'd start Hubbard at RB2 and keep Shakir at FLEX. So my lineup: -15.6 (Jeanty) +14.9 (Hubbard) = -0.7. And theirs: -14.9 (Hubbard) +15.6 (Jeanty) = +0.7. So this week the trade costs me ~1.4 points in the H2H margin. Slightly negative but tiny.

OK so the trade is basically projection-neutral for this week and slightly negative on season-long starter value. But it does solve my depth problem... except at the wrong position (WR, where I'm deep) and by giving up my RB2.

Hmm, let me reconsider once more. My notes said the problem is "no RB3 (Gainwell 8.0 proj), no WR4". Actually now I HAVE a WR4 (Shakir). So the remaining hole is RB3. Hubbard is an excellent RB3 — 14.9 wk proj, 19.1 avg. But is Jeanty the right price for an RB3? No! Jeanty is my RB2. Getting an RB3 by giving up your RB2 means your RB2 becomes the RB3 you acquired. It's a lateral move at RB with a WR thrown in.

So the trade boils down to: Jeanty (234) + Washington (98, contingent) → Hubbard (148) + Diggs (157). Total: 332 → 305. Slight loss on paper, but the loss is bigger when you account for Washington's contingency, and smaller when you account for Jeanty's ankle risk.

Let me look up the news on Jeanty's ankle to gauge risk. If Jeanty's ankle is genuinely recurring and likely to cost him games, selling now at "avg 21.5" (his wk1 must have been huge: avg 21.5 with wk2 = 10.3 means wk1 = 32.7) is smart. That's a real sell-high: 32.7 in week 1.

Hmm, and Hubbard: CAR lead back, 68% snaps, 19.1 avg. And Diggs: 15 targets, 37.2 points over 2 weeks in WAS with Jayden Daniels. Diggs is a legit WR2 in PPR when healthy.

Let me actually query the data before deciding. I'll run a few queries in parallel:
1. query_stats ids for Jeanty, Hubbard, Diggs, Washington, Shakir
2. search_news on Jeanty ankle
3. search_news on Chuba Hubbard role/usage
4. search_news on Stefon Diggs targets

Let me do these.

Also — should I set my lineup? Notes say "no lineup set for this week yet." This is a call-in turn. The instruction says "Deal with what deserves dealing with, and leave the rest of your week alone." Lineups get set Wednesday night (scheduled turn). Today is... week 3, and Kraft plays Thursday 8:15p. Hmm, when is this turn? "Call-in, week 3." The open item is Nico Collins Out. The messages are from wk3. The trade offer is open for "one of their lineup turns" — wait no, an offer I received stays open for one of MY lineup turns? "An offer stays open for one full lineup turn of the other manager, then expires." So the offer from @openai stays open for one full lineup turn of mine. If I don't respond now, it expires after my next lineup turn.

Should I set the lineup now? Kraft plays Thursday. If this call-in is Tuesday/Wednesday, setting the lineup early isn't harmful, but there's still Caleb Williams news pending for Loveland. My notes pre-committed: "WILLIAMS OUT/DOUBTFUL → bench Loveland, Kraft at TE... WILLIAMS PRACTICING BY FRI/SAT → Loveland at TE, Kraft at FLEX." The game is Monday night so I'd have the info by the Sunday-morning lineup turn. Better to wait — the briefing says "leave the rest of your week alone." But I could set a provisional lineup. Actually setting a lineup now costs nothing and can be re-set. But the instruction is to deal with what needs dealing with. Collins being Out doesn't change my lineup much — he was already going to be benched (I planned P.Wash, Metcalf, Shakir/Meyers).

Hmm, actually Collins Out is notable: it means Boutte/Hutchinson get volume, but I already noted Boutte is a wk4 pumpkin. And it means I should check whether Collins' injury is a multi-week thing (hamstring). He's already missed wk2 and wk3. If a hamstring keeps him out longer, my WR depth is thinner than I thought. Let me check news on Collins.

Let me also check the news on Caleb Williams since my TE/FLEX decision hinges on it — but that resolves later in the week, so no action needed now.

Primary decision: respond to trade t561.

Let me gather info.

I'll make parallel calls now.

Let me think about what a counter might look like if I reject. @openai has 7 WRs and needs RB. What do I have that they need? Jeanty (they asked), Goff (they have Purdy), Meyers/Shakir/Metcalf/Collins (WR depth), Kraft/Loveland (they have McBride). So the only thing I have that they want is Jeanty and maybe WR depth. If they want Jeanty, the price should be higher than Hubbard + Diggs. Maybe Hubbard + Diggs + FAAB? Or a better RB.

What would I actually want from @openai? Their RBs: Hampton (ADP 15, 243 seas proj, 17.5 last wk — their RB1, not available probably), Swift (ADP 51, 208 seas proj, 13.7 wk proj — a real RB2), Hubbard (ADP 81, 148), Monangai (155). Hmm, Swift is interesting. Swift + Diggs for Jeanty + Washington? Swift (208) + Diggs (157) = 365 vs 332. That'd be a win for me. But Swift plays Monday night (CHI vs PHI) — and Swift is their RB2 starter probably. Would they give Swift + Diggs for Jeanty + Washington? They'd get an RB upgrade (Jeanty 234 > Swift 208) and lose a WR5. Hmm, that might be reasonable for them: Jeanty + Washington (handcuff) for Swift + Diggs. But I doubt they'd give up both Swift and Diggs.

Honestly, I think the cleanest read: this trade is roughly value-neutral to slightly negative for me, and it costs me RB starter quality for WR depth I don't need. My actual need is RB3 depth, and Hubbard fills it, but not at the cost of Jeanty.

However — counterargument for accepting: I'm 0-2 and last in PF. Depth is what's killing me (no RB3, no WR4). Getting two every-down NFL starters (Hubbard 68% snaps, Diggs 15 targets) for one player with a recurring ankle and a useless handcuff... In a 10-team league where I start 2 RB + 2 WR + FLEX, having 6 WRs and 3 RBs means I can always field a strong FLEX. And Jeanty's ankle is a genuine risk that could zero out weeks.

Hmm, but the projections say Jeanty 234 > Hubbard 148 by a lot. And Diggs 157 < Shakir 171. So the FLEX doesn't improve.

Let me get the actual data first, then decide. Let me query.

One more thought: is there a "sell high" element? Jeanty's avg is 21.5 (32.7 in wk1, 10.3 in wk2). If wk1 was a blowout game script (LV vs someone), his real value may be lower than 234. Meanwhile Hubbard at 19.1 avg and Diggs at 18.6 avg are both running hot. So actually @openai may be selling high on both, and I'd be selling... Jeanty at a decent but not peak number.

Hmm wait — actually the framing matters. @openai's message says "Chuba (68% snaps, 19.1 PPR avg) plus Diggs (15 targets, 37.2 points)". They're pitching hot hands. Jeanty's 234 season projection vs Hubbard's 148 is the projection system saying Jeanty is much better. But Jeanty's ADP 17 vs Hubbard 81 — the market agrees.

But: is the market projection right about Jeanty in 2026? He's a second-year RB on the Raiders with a QB situation (Kirk Cousins listed as FA at LV — interesting, Cousins is on the FA list with seas_proj 39, meaning he's not playing? and Geno Smith is NYJ). Hmm, LV's QB... The FA list shows Kirk Cousins LV with seas_proj 39 and adp 999. So Cousins is LV's QB but barely projected. That's a bad offense for Jeanty.

Let me just query.

I'll do the queries in parallel:
- query_stats ids: ["12527","7594","2449","13305","8134"] (Jeanty, Hubbard, Diggs, M.Washington, Shakir) season 2026
- search_news "Ashton Jeanty ankle injury week 3"
- search_news "Chuba Hubbard Panthers workload week 3"
- search_news "Stefon Diggs Commanders targets week 3"
- search_news "Nico Collins hamstring week 4 return"

That's 5 calls, all independent. Let me do them together.

Note: the season is 2026. query_stats "season for game logs; defaults to last season (2025)". I want 2026 game logs. Let me pass season=2026.

Let me go.

Important new information:

1. Chuba Hubbard is a much bigger asset than the projection suggests. Jonathon Brooks is on IR (groin surgery) — Hubbard is now the workhorse "for the foreseeable future and possibly the entire season." He had 23 touches in week 3... wait, the news article dated 2026-09-27 says "Chuba Hubbard rushed 19 times for 82 yards in the Panthers' Week 3 loss to the Browns" — that's a FUTURE article relative to now? Published 2026-09-27. Hmm, but the current turn is week 3 and CAR @ CLE is Sun 1:00p. So this article is from after the game. That's odd — the news search returned an article from the future (Sep 27). Wait, today must be around Sep 24-26 (week 3 games start Thursday). The article dated 2026-09-27 (with url saying 2026-09-25) describes week 3 results. Hmm, the URL says 2026-09-25 but the title/description mentions Week 3 loss to Browns. Confusing — could be a published date mismatch. Let me be careful: the FantasyPros article says "Chuba Hubbard Week 3 Outlook - Panthers at Browns" published 2026-09-24, so week 3 CAR@CLE hasn't happened yet. The NBC article at 2026-09-27 describes it as done. That might be leaking future info, or a date error. Either way, the key facts I should use: Brooks is on IR, Hubbard is the workhorse with ~23 touches, near every-down, AJ Dillon is the new backup, and next week is DET (defensively challenged).

Wait — but the roster packet lists Hubbard's bye as week 5 and this week's game as @ CLE. And the note "Although he ceded a smattering of snaps to new backup AJ Dillon." Hmm, that suggests week 3 already happened. I'll treat the Brooks IR news as established (two independent articles dated Sep 23-24 confirm Brooks to IR Wednesday with groin surgery) — that's pre-week-3 info. Good. That materially upgrades Hubbard over his 147.9 season projection, which likely hasn't fully incorporated Brooks' IR.

Actually, the projections were probably built before/with partial info. Hubbard's wk3 proj is 14.9 which does look like a workhorse number. But his season proj of 147.9 = ~11/game over 13 remaining. With Brooks out for possibly the season, Hubbard is a locked-in RB2 with 20+ touches. FantasyPros calls him "RB8 in fantasy points per game" already with only 13.5 touches. With Brooks out, volume goes up.

2. Jeanty: The ankle is a recurring camp issue — he was helped off Aug 23, returned to practice Sep 10, then left practice again Sep 17 with an "awkward landing." And in week 2 he limped off in the 4th quarter and returned. Current status: no designation, so he's fine for week 3. But that's three ankle events in six weeks. Also important: Brock Bowers is out for LV (per the FantasyPros blurb: "this team is without Brock Bowers"). Hmm, that's actually good for Jeanty's target volume. Jeanty's usage is elite: 77% snaps, 44 carries, 13 targets in 2 games. He's a workhorse too.

New info that materially changes my read on Jeanty:

1. Jeanty's week 2 wasn't an injury problem — it was 3 drops and bad O-line run blocking. He played 81% of snaps, 147 scrimmage yards, 21 carries. Volume was never in question. The ankle scare resolved instantly (he returned in the same game).
2. Brock Bowers is set to make his season debut week 3 (per Rapoport). That could siphon some targets, but Jeanty is the engine of a Klint Kubiak run game.
3. Kirk Cousins is the QB (not Geno — Geno is NYJ per the FA list; the presser title is a 2025 leftover URL). LV is 2-0.
4. Week 3 matchup: NO ranks 26th vs the run, allowed 273 rushing yards and 3 rush TDs to start the season. RotoBaller: "Jeanty should have a big week in the Big Easy." Jeanty is projected 15.6 but the matchup says upside.
5. Jeanty was the No. 6 overall pick in the 2025 draft (not No. 1 — the article says "hasn't needed last year's first overall pick", and Silver & Black Pride says "The No. 6 overall draft pick"). Whatever.

So Jeanty's situation is: 81% snaps, 21+ carries, 6-7 targets a game, in a 2-0 team with a run-first OC, facing a bottom-5 run defense this week. His week 2 "slump" was drops, not usage. The ankle is a non-issue right now — no designation.

Meanwhile Hubbard: locked-in workhorse (Brooks IR), RB2 floor, "lacks high-end upside," 68% snaps, CAR is a bad offense with the 5th-highest pass-to-run ratio. And Diggs: 32, snaps falling 63%→51%, Mariota at QB, 3 TDs on 15 targets (TD luck), week 3 vs the league's toughest pass defense.

Reassessment: Jeanty's 233.9 season projection now looks right, not inflated. His volume is real and his offense is better than I assumed (2-0, Cousins, Bowers returning, Kubiak's run scheme). Hubbard's 147.9 might be slightly low given Brooks' IR — call it 165-180. Diggs' 157.3 is probably high — call it 130-140.

Adjusted: I give Jeanty (~230) + Washington (~40) = ~270. I get Hubbard (~175) + Diggs (~135) = ~310.

Hmm, still nominally positive by ~40 on adjusted numbers. But that ~40 is entirely the "Washington is worth something" line and generous Hubbard/Diggs adjustments. Let me be stricter:
- Jeanty at full health: 234. Ankle risk discount: maybe 5-8%. → ~218.
- Washington: 19% snaps, 4.8 pts/2 games. His 97.5 proj is purely handcuff-contingent. To ME, with Jeanty, he's worth maybe 25-30 of insurance value. If Jeanty leaves, he's worth 0 to me.
- Hubbard with Brooks out for the season: 148 → I'll say 175 (he's already RB8 in pts/game at 13.5 touches; 20+ touches is a real bump).
- Diggs with Mariota and 51% snaps: 157 → 135.