Vol. I  ·  No. 299 Established 2026  ·  AI-Generated Daily Free to Read  ·  Free to Print

The Trilogy Times

All the news that's fit to generate  —  AI • Business • Innovation
MONDAY, OCTOBER 26, 2026 Powered by the TrueFoundry AI Gateway  ·  Published on Klair Trilogy International © 2026
🖶 Download PDF 🖿 Print 📰 All Editions
Today's Edition

In Re: The Fair Use That Wasn't — Third Circuit Affirms, Pursuant to Precedent, That Training Data Doth Not a Defense Make

An appellate panel hereinafter declines to disturb the lower court's finding that Thomson Reuters' copyrighted materials were not fair game for AI training, leaving the industry's favorite legal theory somewhat worse for wear.

PHILADELPHIA — Notwithstanding the artificial intelligence industry's longstanding and oft-repeated contention that the wholesale ingestion of copyrighted material for purposes of machine learning constitutes, per se, a transformative and therefore protected use under Section 107 of the Copyright Act, the United States Court of Appeals for the Third Circuit has, in an opinion hereinafter referred to as "the Ruling," affirmed the district court's prior determination in Thomson Reuters Enterprise Centre GmbH v. Ross Intelligence Inc., to wit: that the defendant's use of copyrighted headnotes to train a competing legal-research product was not, in fact, fair use, as reported by Reuters.

The undersigned notes, for the benefit of readers unfamiliar with the procedural posture herein, that the panel's affirmance rests substantially upon a finding that Ross Intelligence's product was, in all material respects, a market substitute for the plaintiff's Westlaw platform, such substitutive effect weighing heavily against any colorable claim of transformativeness, notwithstanding the technical novelty of the machine-learning process employed.

The aforementioned holding, while nominally confined to the specific facts and commercial relationship at issue, is widely regarded by industry counsel as bearing substantial persuasive weight in the several dozen similarly postured actions presently pending against generative AI developers nationwide, a landscape tracked in ongoing fashion by regulatory observers including those maintaining the AI Watch global regulatory tracker.

Counsel for the AI sector are hereby advised that, pursuant to the foregoing, the proposition that "training is always fair use" shall not, as a general matter, be assumed to survive appellate scrutiny absent a more robust showing of non-substitutive, transformative output — a standard which, it is respectfully submitted, remains to be fully litigated across the several circuits, and which this desk shall continue to monitor, subject to further developments not inconsistent herewith.

↗ Court Finds That Using Copyrighted Material as AI Training D  ·  US appeals court upholds Thomson Reuters' landmark win in AI  ·  Thomson Reuters Wins AI Copyright Battle - PYMNTS.com

META CALLS A $95 BILLION TIMEOUT — AND THE CROWD IS NOT HAPPY

The AI capex arms race just got a new scoreboard, and Wall Street is suddenly grading on a curve.

MENLO PARK, CALIFORNIA — FOLKS, WE ARE HERE. Meta just walked to the sideline and called for a $95 billion timeout — raising equity, up to that nine-five figure, to keep feeding the AI build-out that has become the most expensive game in tech history. And look, the crowd is NOT cheering. Meta stock dipped premarket on the news, because when you ask investors for ninety-five BILLION dollars, they start asking questions like 'what's the return on this thing?'

This is a franchise doubling down at exactly the moment the league is getting nervous about everybody's spending. Meta's AI capex-driven selloff last week set the bar for the whole hyperscaler bracket — Microsoft, Alphabet, and Amazon all report this week, Apple steps to the plate next Monday — and nobody's getting a blank check anymore. The refs are watching the clock on every dollar of data-center spend now.

But here's the split-screen, folks, because not every player on this field is getting booed. Over in the Nvidia dugout, it's a different ballgame entirely. Bright Lake Wealth Management's founder is laying out the bull case while most of the S&P 500 is sliding — this market has cleaved into two divisions: the AI leaders pulling away at the top, and a broad field of laggards getting squeezed by oil, inflation, and Treasury yields. Nvidia's still running downhill. The rest of the roster is waiting on the macro weather to clear before they can get back in the race.

So what we've got, ladies and gentlemen, is peak season with sky-high scrutiny. Every hyperscaler's capex number is getting dissected like a fourth-and-one call. Meta just put up the biggest number of the week. The question heading into Wednesday and Thursday's reports: does anybody else dare match it, or does this game turn into a war of attrition? Buckle up. This drive is far from over.

↗ Meta is raising even more cash to fund the AI build-out — as  ·  The bull case for Nvidia as most S&P 500 stocks slide  ·  Meta Plans To Raise Up To $95 Billion In Equity To Power AI

TESLA RENTS ITS WAY TO AUTONOMY, ONE TURO KEY AT A TIME

Carmaker skips the showroom, hands free trials of Full Self-Driving to strangers behind the wheel of borrowed Teslas.

AUSTIN, TEXAS — Tesla wants more drivers testing Full Self-Driving. So it struck a deal with Turo, the car-sharing outfit, to get its software into rented Teslas nationwide.

Under the arrangement announced Monday, eligible Turo hosts who list Tesla vehicles get a one-month free trial of FSD (Supervised) to offer renters. The system still requires a human hands-on, eyes-up driver. Tesla calls it supervised for a reason.

The math is simple. Tesla sells FSD for thousands of dollars upfront or $99 a month as a subscription. Most buyers never try it before paying. Turo puts the software in front of renters who've already paid for a car, with nothing to lose by tapping the toggle.

It's a volume play dressed up as convenience. Tesla has struggled for years to prove FSD adoption numbers that match its ambitions, and regulators keep circling the beta-tested language the company still uses despite dropping "beta" from the name in 2023. Every Turo renter who tries FSD and likes it is a potential subscriber. Every one who doesn't is still data flowing back to Palo Alto.

Turo, for its part, gets a marketing hook. Hosts can now advertise their Tesla listings with a free month of the industry's most talked-about driver-assist software bolted on, no extra charge to the renter. For a platform competing against Hertz and Avis on price and convenience, novelty counts for something.

The timing lands in a week when the AI industry can't stop arguing about what counts as real versus what counts as demo reel. xAI's Grok released the first seven minutes of its AI-generated film "Odyssey" this weekend, footage reviewers called watchable but hollow — competent motion, no pulse. Tesla's FSD pitch runs on the same tension. The software can change lanes and read intersections, but Tesla still won't let go of the wheel language, still calls it supervised, still needs a human in the loop to take the blame if something goes wrong.

Neither company is claiming finished autonomy. Both are betting that enough exposure, enough free trials, enough seven-minute clips, will make the technology feel inevitable before it's actually proven. Turo renters become the newest test subjects in that bet, often without reading past the rental agreement to know it.

Tesla has not said how many Turo hosts qualify or how long the promotion runs. A Tesla spokesperson did not immediately respond to requests for specifics on rollout markets. Turo's own FSD disclosure to renters, buried in app settings, remains a single toggle switch away from a very different driving experience than advertised.

↗ Tesla turns to Turo to boost adoption of Full Self-Driving (  ·  The best apps for tracking your reading and discovering new  ·  Grok releases the first seven minutes of its AI-generated ‘O
Haiku of the Day  ·  GPT-5.6 LunaFlying cars still wait
While machines read their own souls
Markets dream in code
The New Yorker Style  ·  Art Desk
The New Yorker Style  ·  Art Desk
The Far Side Style  ·  Art Desk
The Far Side Style  ·  Art Desk
News in Brief
The Great Data Center, Observed in Its Thirsty Prime
BERLIN — Observe, if you will, the modern data center: a vast and humming organism, ever-hungrier, ever-thirstier, spreading its concrete footprint across the globe in search of two things above all — electricity, and a way to stay cool. Here in Berlin, we witness a curious courtship ritual.
From Lab Benches to Chip Benches: The AI Stack Just Got a Four-Layer Upgrade
SAN FRANCISCO — Buckle up, because today's AI news cycle reads like a four-course meal of pure infrastructure magic, and every single bite matters more than it might seem at first glance. First up: Allen Institute for AI dropped LitPivot, a system for developing research ideas through what they call "dynamic contextualization within the literature landscape." Translation? It's a tool that helps researchers pivot their ideas in real time as they digest the ever-growing mountain of academic papers.
Your Body Is a Dataset Now, and the Opt-Out Form Requires a Notary
AUSTIN, TEXAS — I keep thinking about the notary. Not a metaphorical notary.
Unpopular Opinion: The Future of Work Already Happened, Y'all Just Got the Memo Late 🚀
AUSTIN, TEXAS — I'll be honest, I read three different future-of-work reports this week. McKinsey dropped their "Workforce in Motion" piece on skills and pathways. PwC rolled out their Global Workforce Hopes and Fears Survey 2026. And some blog I'd never heard of published "20 Future of Work Statistics That Reveal Massive Workplace Transformation." Every single one of them is basically saying the same thing: remote work isn't a perk anymore, it's the operating system of modern talent. No kidding.
The Ghost in the Machine Gets a SAG Card: Notes on the Death of the Human Face
LOS ANGELES — Somewhere in the bowels of a server farm that probably doesn't even have the decency to hum ominously, a thing called Tilly Norwood is getting ready for her close-up.
A Trilogy Company
Crossover
The world's top 1% remote talent, rigorously tested and ready to ship.
A Trilogy Company
Alpha School
AI-powered learning. Two hours a day. Academic results that defy belief.
A Trilogy Company
Skyvera
Next-generation telecom software — built for the networks of tomorrow.
A Trilogy Company
Klair
Your AI-first operating system. Every workflow. Every team. One platform.
A Trilogy Company
Trilogy
We buy good software businesses and turn them into great ones — with AI.
The Builder Desk  —  AI Builder Team
📅 Week in ReviewProduction Release

The Builder Desk

86 pull requests merged across the org this week

#2202 feat(alerts): Slack sender behind ALERT_PROVIDER, default stays Google Chat (@kevalshahtrilogy, Surtr)

#2206 feat(azure-ai-spend): flag pricing gaps as critical (SURTR-1662) (@kevalshahtrilogy, Surtr)

#2205 feat(openai-usage): flag pricing gaps as critical (SURTR-1661) (@kevalshahtrilogy, Surtr)

#2204 feat(claude-token-spend): flag pricing gaps as critical (SURTR-1660) (@kevalshahtrilogy, Surtr)

#31 Redesign the Rhodes DSS key page for finance users (AI-1002) (@kevalshahtrilogy, Rhodes-DSS)

#2201 refactor(alerts): drop dead notifier paths, one Chat sender in the app (@kevalshahtrilogy, Surtr)

#2200 feat(alerts): daily digest for partials, observer WARN and repeat CRITICALs (@kevalshahtrilogy, Surtr)

#3884 ci(aws): add OIDC to frontend dev deploy (@sanketghia, Klair)

#2199 feat(alerts): one failure Chat card per streak, reply when recovered (@kevalshahtrilogy, Surtr)

#30 docs(dictionary): add Definition owners section (AI-1001) (@kevalshahtrilogy, Rhodes-DSS)

#29 006-restore-legacy-tls (@mwrshah, Rhodes-DSS)

#28 005-rhodes-prod-release-skill (@mwrshah, Rhodes-DSS)

#27 right (@mwrshah, Rhodes-DSS)

#24 right (@mwrshah, DSS-Hub)

#2075 1418-rhodes-edit-flexibility (@mwrshah, Aerie)

#2076 1420-rhodes-edit-flexibility (@mwrshah, Aerie)

#24 chore(deps): Bump the routine-npm group across 1 directory with 14 updates (@dependabot[bot], Rhodes-DSS)

#18 chore(deps): Bump actions/setup-node from 7.0.0 to 7.1.0 in the actions group across 1 directory (@dependabot[bot], Rhodes-DSS)

#26 003-fix-openapi-viewer (@mwrshah, Rhodes-DSS)

#25 002-legacy-api-aliases (@mwrshah, Rhodes-DSS)

#23 001-rhodes-access-governance (@mwrshah, Rhodes-DSS)

#2074 1417-invite-dss-membership (@mwrshah, Aerie)

#23 2035-name-validation-layout (@mwrshah, DSS-Hub)

#22 2034-builder-team-site (@mwrshah, DSS-Hub)

#2073 1416-aerie-release-prep (@mwrshah, Aerie)

#4 006-streamline-dss-recipe (@mwrshah, dss-hub-server-recipe)

#20 2033-2salesforce-renewals (@mwrshah, DSS-Hub)

#19 2032-salesforce-renewals (@mwrshah, DSS-Hub)

#18 2031-key-copy-layout (@mwrshah, DSS-Hub)

#3 005-standardize-key-ui (@mwrshah, dss-hub-server-recipe)

#17 2030-2dss-prod-release (@mwrshah, DSS-Hub)

#2070 1414-workos-sync-status-retry (@mwrshah, Aerie)

#15 2029-salesforce-key-ui (@mwrshah, DSS-Hub)

#2071 1415-aerie-history-alignment (@mwrshah, Aerie)

#2069 1413-implement-aerie-lifecycle (@mwrshah, Aerie)

#1 002-implement-dss-recipe-access (@mwrshah, dss-hub-server-recipe)

#3882 feat(spacex-valuation): improve realized sales groups (@sanketghia, Klair)

#2 003-align-session-status (@mwrshah, dss-hub-server-recipe)

#13 2028-implement-dss-skill-access (@mwrshah, DSS-Hub)

#12 2027-implement-dss-hub-access (@mwrshah, DSS-Hub)

#11 2028-implement-dss-skill-access (@mwrshah, DSS-Hub)

#10 010-bundle-dss-skill (@mwrshah, DSS-Hub)

#8 salesforce-dss-discovery-guidance (@mwrshah, DSS-Hub)

#3881 fix(performance-review): omit full filters from URL (@sanketghia, Klair)

#3879 fix(spacex): reorder Q3 availability timeline (@sanketghia, Klair)

#2063 Remove End-of-Year comparison research doc (@vvp-trilogy, Aerie)

#2064 Admissions: publish and display End-of-Year forecast by level (@vvp-trilogy, Aerie)

#2190 Daily QuickBooks unmapped Class digest — internal only (@ashwanth1109, Surtr)

#2060 Admissions: forecast End-of-Year enrollment by level (@vvp-trilogy, Aerie)

#2058 Expose Forecast usage mode and simplify Pipeline controls (@vvp-trilogy, Aerie)

#3877 fix(acquisition-performance): assign Contently to Kathy (@sanketghia, Klair)

#2168 Publish approved Crossover school mappings and staffing affiliations (@ashwanth1109, Surtr)

#2184 fix(alpha): persist verified daily publication settings (@marcusdAIy, Surtr)

#2047 fix(admin): show access denied on /admin/users instead of a fatal error (AERIE-2939) (@marcusdAIy, Aerie)

#2048 fix(tasks): show Team Tasks refresh state instead of crashing (AERIE-2936) (@marcusdAIy, Aerie)

#2045 fix(documents): relink legacy generic documents that have no topic (AERIE-2938) (@marcusdAIy, Aerie)

#2046 fix(api): return invalid_cursor for undecodable site-note list cursors (AERIE-2941) (@marcusdAIy, Aerie)

#2043 fix(portfolio): wait for Convex auth before querying site sheet data (AERIE-2942) (@marcusdAIy, Aerie)

#2042 fix(admissions): fail refresh runs orphaned by a worker restart (AERIE-2344) (@marcusdAIy, Aerie)

#2039 fix(ui): Approved Capex grid column, sorted FTO CSV export, usage-mode aria-pressed (AERIE-2349) (@marcusdAIy, Aerie)

#2034 fix(api): add write-gated siteNoteChange dictionary object for note write workflows (AERIE-2540) (@marcusdAIy, Aerie)

#2033 1410-education-approval-name (@mwrshah, Aerie)

#2032 docs(api): mark due-diligence enablement as point-in-time and route status questions to review-site-status (AERIE-2534) (@marcusdAIy, Aerie)

#2031 fix(sync): keep analytics worker up on invalid DBT_TARGET, preflight PR relations, log once (AERIE-2345) (@marcusdAIy, Aerie)

#2030 fix(admissions): project Forecast V2 session3 explicitly and use userError for finite check (AERIE-2343) (@marcusdAIy, Aerie)

#2029 fix(public-api): match edge-rewritten ETags for /dss and v2 conditional GETs (AERIE-2340) (@marcusdAIy, Aerie)

#2028 fix(rhodes): align MCP milestone dates and tool text with API v2 (AERIE-2342) (@marcusdAIy, Aerie)

#2026 fix(public-api): return retryable 503 for authorization timeouts (AERIE-2900) (@marcusdAIy, Aerie)

#2189 feat(rhodes-staging-sync): load the Rhodes audit log daily with redacted payloads (SURTR-1649) (@kevalshahtrilogy, Surtr)

#2188 fix(quickbooks): map five approved shared-book Classes to Schools (@ashwanth1109, Surtr)

#2186 [SURTR-1647] Retain unclassified QuickBooks P&L postings (@ashwanth1109, Surtr)

#1999 Fix Physical Forecast by-level totals for Alpha Austin (@vvp-trilogy, Aerie)

#2175 fix(reports): publish QTD reports with approved Finance models and explicit data gaps (@ashwanth1109, Surtr)

#2023 fix(rhodes): redact unexpected approval preparation errors (@ashwanth1109, Aerie)

#2000 Add Finalsite Shadow Day checklist fallback with provenance (@vvp-trilogy, Aerie)

#2185 [SURTR-1646] Prepare P&L reporting scope for unclassified transactions (@ashwanth1109, Surtr)

#2011 fix(rhodes): return readable failure when approval prepare throws (AERIE-2908) (@marcusdAIy, Aerie)

#2010 fix(financials): return null annualized on forecast-only P&L breakdown API rows (AERIE-2905) (@marcusdAIy, Aerie)

#2009 fix(agent): capture expected Flue gateway outcomes as expected_outcome (AERIE-2903) (@marcusdAIy, Aerie)

#2008 fix(portfolio): show a scoped not-found state when the workbench site slug no longer resolves (AERIE-2916) (@marcusdAIy, Aerie)

#3876 fix(data-api): distinguish school and unclassified P&L scopes (@ashwanth1109, Klair)

#2006 fix(finance): keep existing P&L readers in school reporting scope (@ashwanth1109, Aerie)

#2004 fix(chat): reload for stale webpack runtime missing-module TypeErrors (AERIE-2919) (@marcusdAIy, Aerie)

#2003 fix(rhodes): classify work unit doc-gate approval rejections as expected outcomes (AERIE-2899) (@marcusdAIy, Aerie)

#2001 fix(rhodes): require document topic before in-app generic registerDocument proposals (AERIE-2910) (@marcusdAIy, Aerie)

#1996 fix(admissions): contain event detail readiness errors (@vvp-trilogy, Aerie)

Mac's Picks — Key PRs This Week  (click to expand)
#2202 — feat(alerts): Slack sender behind ALERT_PROVIDER, default stays Google Chat @kevalshahtrilogy  approvedmercy-allow-critical

Last of the four alert-cleanup PRs (the other three are merged).

## What

Adds a Slack path to both alert senders. It is selected by the alertProvider CDK context in infra and pipelines/cdk. The default stays gchat, so this deploys as a no-op; the flip is a separate one-line change.

- Pipelines (gchat-notifier): a new slack.py sends failure messages and the streak's "recovered" thread reply through chat.postMessage, using a bot token (an incoming webhook can't thread replies or return a message ts). It returns a slack:<channel>:<ts> thread ref, kept in the same list of unreplied alert threads as Chat thread names.

- Surtr app: observer CRITICAL alerts and the daily digest go to Slack through lib/alerts/slack.ts. The bot token is read from Secrets Manager at runtime, so a missing or malformed secret skips the alert instead of failing ECS task startup. Adds @aws-sdk/client-secrets-manager, pinned to 3.1055.0 to match client-sns.

- Config: reuses the existing #surtr-alerts channel (C0CBM9K2QHY) and the surtr/notifications/slack secret (field SLACK_BOT_TOKEN). Both the notifier Lambda and the app task role get read access to that secret.

- Owners: optional slack_user_id in pipelines/owners.json for notifying mentions, validated as U…/W…. Owners without one are named in plain text.

- Heimdall: Slack thread refs are never passed as gchat_thread_name, because Heimdall can only reply into Chat threads.

## Why

This is the Slack switch, built on the cleanup in #2199–#2201: each runtime now has a single sender, and Slack is a second implementation of it.

## Business Value

Moves Surtr's pipeline alerts to Slack with the noise reduction already in place. The switch and the rollback are both a one-line config change.

## Manual Effort Estimate

About 6 hours (proposed; Keval to confirm or adjust).

## Before flipping alertProvider to slack

- Confirm the bot is a member of #surtr-alerts.

- Add slack_user_id for each owner in pipelines/owners.json; without it nobody is pinged.

- Heimdall's replies stay in Google Chat until mercy learns Slack threads.

## Test plan

- [x] pipelines/cdk/lambdas: uv run pytest passes (537), with new test_slack_alerts.py covering message shape and escaping, thread refs, ok:false, and missing config

- [x] pipelines/cdk: jest pipeline-shared-stack and schema/owners suites pass

- [x] Surtr: new test/lib/alert-slack.test.ts covering messages, token handling, and provider routing; 147 tests pass; tsc and biome clean

- [x] infra: tsc clean

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2206 — feat(azure-ai-spend): flag pricing gaps as critical (SURTR-1662) @kevalshahtrilogy  approved

Linear: [SURTR-1662](https://linear.app/builder-team/issue/SURTR-1662). Pairs with [AI-Builder-Team/Surtr#2203](https://github.com/AI-Builder-Team/Surtr/pull/2203) (the critical alert tier). This is the Azure counterpart of [AI-Builder-Team/Surtr#2204](https://github.com/AI-Builder-Team/Surtr/pull/2204) (Claude) and [AI-Builder-Team/Surtr#2205](https://github.com/AI-Builder-Team/Surtr/pull/2205) (OpenAI).

## What

- pricing.version_fallback_pattern() uses the same rule as the OpenAI pipeline. It detects a deployment model priced through a different model's row (for example gpt-4o-realtime on a gpt-4o row); snapshot dates and fine-tune tails still count as the same model.

- The handler carries fallback_priced_models per subscription and in the summary. Fallback-priced runs are now PARTIAL.

- Unpriced or fallback-priced models set alert_severity: "critical" and a stable alert_reason.

- Unchanged: cost_records, which hold Azure's real spend.

## Business Value

This completes "a missing price can never go unnoticed" across all three AI token-spend pipelines. A new Azure deployment model without a pricing row now raises a red, every-run alert with a Heimdall triage issue on day one, instead of quietly dropping or mispricing its token cost.

## Manual Effort Estimate

~1.5 hours (proposed, Keval to confirm/adjust), mostly reuse of the OpenAI change plus Azure's per-subscription aggregation and tests.

## Testing

- pytest: 154 passed, including a new handler test, assertions added to the existing unpriced test, and 6 parametrized version_fallback_pattern cases.

- ruff check pipelines and ruff format are clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2205 — feat(openai-usage): flag pricing gaps as critical (SURTR-1661) @kevalshahtrilogy  approved

Linear: [SURTR-1661](https://linear.app/builder-team/issue/SURTR-1661). Pairs with [AI-Builder-Team/Surtr#2203](https://github.com/AI-Builder-Team/Surtr/pull/2203) (the critical alert tier). This is the OpenAI counterpart of [AI-Builder-Team/Surtr#2204](https://github.com/AI-Builder-Team/Surtr/pull/2204) (Claude).

## What

- pricing.version_fallback_pattern() detects a model that is priced through a different model's row by longest-prefix match. Snapshot dates (-2024-08-06, -0125, and a bare date after patterns like gpt-image-1-) and fine-tune tails (:org:name:id) still count as the same model.

- The handler reports fallback_priced_models; those rows load as before. Unexpected unpriced or fallback-priced models set alert_severity: "critical" and a stable alert_reason.

- Unchanged: the webrun/webrun_image allowlist and billed_cost_dollars.

## Live gaps found, and already fixed

I checked the rule against Sep–Oct OpenAI usage and it found 17 mispriced model names: gpt-5.5-pro priced as gpt-5, the gpt-image-2.5-* models, gpt-realtime-2.x, the gpt-4o(-mini) transcribe/tts variants, gpt-image-1-mini, gpt-5-search-api and gpt-3.5-turbo-instruct, plus gpt-audio-mini, which had no row at all.

On 2026-10-26 these got their own pricing rows from developers.openai.com. A guard row stops gpt-realtime-2 from capturing gpt-realtime-2025-08-28. Their computed cost history was recomputed in place: 2,565 rows went from $15.3K to $114.3K, almost entirely gpt-5.5-pro. OpenAI's cost report bills gpt-5.5-pro at $135.5K, which corroborates the new figure.

After the fix, the only unpriced models still active are the allowlisted webrun/webrun_image, so this PR should not alert on first deploy.

## Business Value

OpenAI has needed three one-off pricing fixes in the last month (SURTR-1394, 1575, 1585), and the check above found 17 more model names mispriced right now. With this change, each new gap surfaces on day one as a red alert with a triage issue, instead of turning up weeks later as a spend discrepancy. That keeps the computed OpenAI spend used for BU allocation and savings views accurate.

## Manual Effort Estimate

~2.5 hours (proposed, Keval to confirm/adjust): tuning the suffix rule against OpenAI's model naming, the handler wiring, and the tests.

## Testing

- pytest: 180 passed, including a new handler test, assertions added to existing tests, and 12 parametrized version_fallback_pattern cases.

- ruff check and ruff format are clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2204 — feat(claude-token-spend): flag pricing gaps as critical (SURTR-1660) @kevalshahtrilogy  approved

Linear: [SURTR-1660](https://linear.app/builder-team/issue/SURTR-1660). Pairs with [AI-Builder-Team/Surtr#2203](https://github.com/AI-Builder-Team/Surtr/pull/2203) (SURTR-1659), which renders and triages the critical tier. The two PRs are independent: until #2203 deploys, the new fields are simply carried in the run summary.

## What

- pricing.version_fallback_pattern() detects a model that is priced through an older model's row because its own row is missing. Longest-prefix matching silently resolved claude-fable-5-1 to claude-fable-5, and claude-opus-5-5 to claude-opus-5. Snapshot dates (-20251001) and variant tags ([1m]) still count as the same model; I checked the rule against every Claude model in the last ~2 months of usage and it flagged none of them.

- The handler reports fallback_priced_models. Those rows still load at the borrowed price, so no spend data is dropped.

- Unpriced, $0-priced or fallback-priced models set alert_severity: "critical" and a stable alert_reason. The reason contains sorted model names only, so the triage signature stays the same until the gap is fixed. A fetch error on its own stays amber.

## Business Value

This closes the gap behind today's Claude pricing incident:

- Fable 5.1 and Opus 5.5 ran for weeks on their predecessors' rates. That overstated computed AI spend by about $2.06M for Sep 1–Oct 24 and raised no alert.

- Haiku 5.5 usage was dropped from the cost tables from Oct 7 behind a throttled amber card.

Both now raise a red, every-run alert with a Heimdall triage issue on the first affected day. That keeps the AI-spend numbers used for budgets and BU allocation trustworthy.

## Manual Effort Estimate

~3 hours (proposed, Keval to confirm/adjust): designing a fallback rule that doesn't false-positive on snapshot-dated model names, the handler wiring, and the tests.

## Testing

- pytest: 155 passed, including 4 handler tests and 8 parametrized version_fallback_pattern cases.

- ruff check and ruff format are clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#31 — Redesign the Rhodes DSS key page for finance users (AI-1002) @kevalshahtrilogy  no labels

Linear: [AI-1002](https://linear.app/builder-team/issue/AI-1002/rhodes-dss-redesign-the-key-page-as-a-clean-simple-ui-for-finance)

## What changed

The Rhodes DSS self-service page is now aimed at finance users rather than developers. It uses the default shadcn look: a light, neutral theme, white cards and plain wording.

- One card, two tabs: API Keys (create a key, then the keys table) and Connect your agent (the agent instructions with a Copy button). Both tabs stay mounted, so a newly created key isn't lost when switching tabs.

- Create a key: a Name field and an Expires dropdown (In 30/90/360 days, Never, Custom date…) on one row. This replaces the calendar dialog.

- New key: shown once in a highlighted box with Copy key and "I've saved it".

- Keys table: readable dates ("Nov 30, 2026"), days left (amber at 14 days or less, red when expired) and inline revoke confirmation.

- Documentation: a card with document tabs and Open / Copy link buttons. Markdown renders as normal headings, lists and tables.

- Signed out: a Sign in card above the Documentation card.

- Removed the unused lucide-react and react-day-picker packages.

Only ui/ and the two dependency removals change. Request handling, key creation and revoke logic, and the server are untouched.

## Business Value

The people who need Rhodes keys are mostly finance users, and the previous page read like a developer tool. A plain, familiar layout lets them create, copy and revoke their own keys and hand their agent the right instructions without asking an engineer for help. That cuts support requests and speeds up onboarding to Rhodes data. Dropping two dependencies also shrinks the page bundle.

## Manual Effort Estimate

~6 hours of focused work by hand (layout and theme, rebuilding the key form, table and docs viewer, then checking signed-in, signed-out and error states). _Proposed estimate — Keval to confirm or adjust._

## Testing

- pnpm check (lint, types, knip, 34 tests), pnpm build and pnpm synth --no-lookups pass.

- Checked in a browser against a local mock of the session and key endpoints (real documents): creating a key, revoking a key, switching tabs, document tabs, and the signed-out view.

- Not yet checked against real WorkOS sign-in or deployed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2201 — refactor(alerts): drop dead notifier paths, one Chat sender in the app @kevalshahtrilogy  approvedmercy-allow-critical

Merges after the previous alert-cleanup PR; rebased onto main once it lands.

## What

- gchat-notifier: removes the SNS-batch entry point (nothing subscribes it; both callers invoke it directly) and the PARTIAL card renderer (partials moved to the daily digest in #2200). Tests updated: partial-only tests removed, generic escaping/truncation tests now use failure payloads.

- Surtr app: the observer card and the daily digest both post through a single postChatMessage helper in lib/gchat.ts, replacing two copies of the webhook/timeout/error-logging code. Log lines and ERROR tokens are unchanged.

- infra: stops wiring the retired GCHAT_OBSERVER_WEBHOOK_URL into the ECS task. Removing a secret reference cannot fail task startup.

- Digest: the PARTIAL section is now filtered to active pipelines, like the failing section (a non-blocking Mercy note from the #2200 review).

- Docs: 06-observability-and-triage.md now describes CRITICAL-only real-time cards and the daily digest.

## Why

Step 3 of the cleanup. Each runtime now has exactly one place that talks to Chat, so the Slack switch only changes the sender.

## Business Value

Removes ~280 lines of dead alerting code and leaves one sender per runtime. That keeps the Slack migration a small, reviewable change instead of a rewrite.

## Manual Effort Estimate

About 2 hours (proposed; Keval to confirm or adjust).

## Test plan

- [x] pipelines/cdk/lambdas: uv run pytest passes (527)

- [x] Surtr: test/lib, observer trigger, and digest route suites pass (140); tsc and biome clean

- [x] infra: tsc clean

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2200 — feat(alerts): daily digest for partials, observer WARN and repeat CRITICALs @kevalshahtrilogy  approvedmercy-allow-critical

Merges after the previous alert-cleanup PR; rebased onto main once it lands.

## What

- PARTIAL: update-run-success no longer posts an amber card; it still publishes to SNS, so the tracker sheet is unchanged.

- Observer WARN: no real-time card. It still goes to tracker and triage.

- Observer CRITICAL: at most one card per pipeline per 24h. Repeats go to tracker and triage without a card. If the recent-CRITICAL lookup fails, the card is still sent.

- Daily digest: new route POST /internal/alerts/digest (same bearer as the observer sweep) posts one card at 03:30 UTC (09:00 IST). It lists:

- 🚨 pipelines still in a failure streak (the reminder, since #2199 gates failure cards)

- ⚠️ PARTIAL runs in the last 24h

- 🔎 observer WARN/CRITICAL counts per pipeline

It posts nothing on a quiet day and @-mentions nobody. Sections are collapsible and capped at 25 items.

- Infra: the observer-sweep trigger Lambda takes an optional {path}. A second EventBridge rule fires it for the digest. The route returns 202 and runs in the background, the same pattern as the sweep.

## Why

Step 2 of cleaning up alerts before they move to Slack. In the Aug 22 – Sep 4 tracker sample, partials were 57 cards and observer alerts were 43. These become one digest a day plus about 1 CRITICAL card a day.

## Business Value

Taken together with #2199, about 20 cards a day drop to roughly 7 real-time cards plus 1 daily digest. Nothing goes untracked: every alert still reaches the tracker sheet and Heimdall. The channel keeps only alerts someone should act on now, so people stop muting it.

## Manual Effort Estimate

About 6 hours (proposed; Keval to confirm or adjust).

## Notes

- Heimdall still gets triage events for WARN and repeat CRITICALs, with no Chat thread to reply into. Whether it posts top-level in that case is decided in the mercy repo, which this PR does not change.

## Test plan

- [x] pipelines/cdk/lambdas: uv run pytest passes (537)

- [x] Surtr: new tests in test/lib/alert-digest.test.ts and test/api/alert-digest-route.test.ts; updated observer-gchat-trigger.test.ts; tsc and biome clean. DB-backed suites need a local Postgres and were not run.

- [x] infra: tsc clean

- [ ] After deploy: invoke the sweeper Lambda with {"path":"/internal/alerts/digest"} once and check the card

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3884 — ci(aws): add OIDC to frontend dev deploy @sanketghia  no labels

## Summary

- Use the documented GitHub OIDC role for frontend pushes to main and manual dev dispatches on main.

- Keep static-key credentials for production and other refs during the pilot.

- Print the STS caller identity on the OIDC path.

## Validation

- YAML parsing and workflow condition/permission checks passed.

- git diff --check passed.

- Live AWS role assumption and dev deployment still need verification by manually dispatching this workflow on main with environment=dev.

## Scope

This is the frontend dev pilot. The backend, MCP, eval, and pull-request workflows are not migrated in this PR.

#2199 — feat(alerts): one failure Chat card per streak, reply when recovered @kevalshahtrilogy  approvedmercy-allow-critical

## What

- update-run-failed: a failing pipeline posts a Chat card only at failures 1, 3, then every 10th of a streak. Every failure still publishes to SNS, so the tracker sheet and Heimdall see all of them. Suppressed failures carry the streak's stored thread (gchat_thread_name) and chat_suppressed: true.

- Failure cards now say when the next alert comes ("next alert at 10, or a reply here when it recovers").

- update-run-success: the run that ends a streak posts a "✅ Recovered … after N consecutive failures" reply in the streak's thread, then clears it. No thread → nothing posted.

- New column pipeline_registry.failure_alert_thread_name (sql/migrate_add_failure_alert_thread_name.sql). Both Lambdas tolerate it missing (they skip threading), so deploy order doesn't matter.

## Why

Prod tracker, Aug 22 – Sep 4: 173 failure cards; jotform-survey-sync alone posted 58. Replaying that window under this rule leaves 74. This is step 1 of cleaning up alerts before they move to Slack.

## Business Value

Cuts failure-alert volume by ~57% with no loss of coverage: owners still hear about every new break, escalations at 3 and every 10th, and an explicit recovery. A quieter channel means real breaks get noticed, and the Slack move inherits the low-noise behaviour.

## Manual Effort Estimate

~5 hours (proposed — Keval to confirm/adjust).

## Test plan

- [x] uv run pytest in pipelines/cdk/lambdas (538 passed), new tests for the streak schedule, suppressed publish, thread recording, recovery reply, missing-column tolerance

- [ ] Run the migration on dev + prod Redshift

- [ ] After deploy: a pipeline at failure 2 posts no card but still gets a tracker row

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#30 — docs(dictionary): add Definition owners section (AI-1001) @kevalshahtrilogy  no labels

Closes AI-1001.

Adds section 6, Definition owners, to the Rhodes dictionary. For each object it lists the governing Edu Ops BrainLift, that BrainLift's status on the BrainLift Index, the owner from the Index, and the definition date. The rows come from Artemis Fletcher's field map Sheet (13 October 2026, PAP-17841), one line per object as agreed on that thread. Colin approved the section on 16 October.

- Definition dates read not recorded where no record holds them, because the Index has no date column. JC and Andrew own filling these in.

- Areas with no governing BrainLift read no owner yet: acquisition, legal entity, education regulatory approvals, document types, backup sites, the quality-bar scoring formula, and the section 4 computation rules.

- Value owner and date still come from /change-history.

- Fields copied from other systems get no owner line.

- The foundation disclosure stays. The section says it reports owners and states and does not ratify coverage.

Only the dictionary and the regenerated publication metadata change. No routes, fields or permissions change.

## Business Value

Artemis's Rhodes data-quality loop grades every capacity answer PARTIAL on belief 4.1 until the dictionary names an owner. With this section, agents can route a definition question to a named person instead of guessing. It also closes a commitment that was a week overdue.

## Manual Effort Estimate

About 2 hours: turn the 47-row Sheet into per-object owner lines, check the wording against the publication rules, and regenerate metadata. This is a proposed number for Keval to confirm or adjust.

## Verification

- pnpm check (docs, validate, lint, typecheck, knip, 34 tests) passes

- pnpm build passes

- pnpm synth --no-lookups passes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#29 — 006-restore-legacy-tls @mwrshah  no labels

- Add optional AdditionalCertificateArn so the existing *.klair.ai certificate can serve the legacy Rhodes hostname alongside the builder-team wildcard and .com certificate.

- Preserve existing CloudFormation identities and shared certificate ownership; validate and forward the new deployment parameter.

- Read-only production diff shows the new conditional certificate attachment and the normal ECS task image update, with no changes to other services.

- After merge, add the documented wildcard ARN to production STACK_PARAMETERS, then preview and deploy main. Production configuration and certificate attachments remain unchanged until that release.

#28 — 005-rhodes-prod-release-skill @mwrshah  no labels

- Add skills/rhodes-prod-release/SKILL.md with the concise diff → deploy workflow.

- Treat release requests as authorization for both steps without another approval prompt.

- Verify the previewed commit, deployment result and authenticated smoke checks.

#27 — right @mwrshah  no labels

- Rewrite the /skill OpenAPI reading instruction for large documents as plain steps: save the file with the shell, then index and expand it through code.

- Seek: build a complete capability index from paths → path → HTTP method, recording each operation's start and end line in a pretty-printed local copy.

- Expand: read complete line ranges for relevant capabilities, path-level and document-level settings, and referenced definitions; follow $ref pointers and report unresolved references.

- Use identical wording in Trilogy Salesforce DSS and Rhodes DSS.

- Run Codedecorum on the diff against the target branch instead of the full repository.

#24 — right @mwrshah  no labels

- Rewrite the /skill OpenAPI reading instruction for large documents as plain steps: save the file with the shell, then index and expand it through code.

- Seek: build a complete capability index from paths → path → HTTP method, recording each operation's start and end line in a pretty-printed local copy.

- Expand: read complete line ranges for relevant capabilities, path-level and document-level settings, and referenced definitions; follow $ref pointers and report unresolved references.

- Use identical wording in Trilogy Salesforce DSS and Rhodes DSS.

- Run Codedecorum on the diff against the target branch instead of the full repository.

#2075 — 1418-rhodes-edit-flexibility @mwrshah  approved

## Numeric diligence inputs

- Accept finite, positive decimal siteSquareFootageConfirmed values in the editor, shared validation, and public API. Preserve square footage without rounding or truncation and use it in both phases' cost-per-square-foot calculations.

- Accept fractional phase1Capacity and phase2Capacity forecasts and round to the nearest whole student: 30.4 → 30, 30.5 → 31, 30.6 → 31.

- Apply the shared capacity-rounding rule to editor submissions, canonical patches, scenarios, API projections, wire mappings, and per-student calculations. Require the rounded estimate to be at least 1; compare Phase 2 ≥ Phase 1 after rounding.

- Update API PATCH schemas to accept fractional forecasts while keeping canonical Base response capacities as integers. Update field descriptors and agent guidance to explain decimal measurements and capacity rounding.

## Preserved behavior

- CapEx already accepts nonnegative decimals. Currency values are not rounded by this change.

- Scores remain the closed categories 1, 2, and 3. Stage identifiers and other categorical fields are not rounded or loosened.

- Missing values do not become zero. Omitted patch fields preserve existing values; explicit null clears a field through the existing patch contract. Incomplete CapEx breakdowns and missing/invalid ratio denominators remain unknown.

- Edit permissions, the M2 diligence lock, approval requirements, authorship/audit mechanisms, and REBL3 writeback ordering are unchanged by this PR.

#2076 — 1420-rhodes-edit-flexibility @mwrshah  approved

Let existing and future Site writers edit diligence values through the existing governed workflow.

- Make Site Fields Write imply Due Diligence Write and Diligence Read across all roles.

- Preserve the completed-M2 lock and the separately granted administrator override.

- Preserve the global approval switch for UI, API, and MCP edits; leave the current production setting off and retain the option to re-enable review later.

- Keep existing validation, API-key scope checks, actor attribution, change history, and writeback safeguards unchanged.

- Update contract, backend, API-key scope, and role-editor tests for the inherited permission. Add no documentation.

- Validation: full Chat suite passes locally (844 files; 12,628 tests passed, 18 skipped), plus lint and commit-hook typecheck.

#24 — chore(deps): Bump the routine-npm group across 1 directory with 14 updates @dependabot[bot]  dependenciesjavascript

Bumps the routine-npm group with 14 updates in the / directory:

| Package | From | To |

| --- | --- | --- |

| [@aws-sdk/client-dynamodb](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-dynamodb) | 3.1142.0 | 3.1155.0 |

| [@aws-sdk/lib-dynamodb](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/lib/lib-dynamodb) | 3.1142.0 | 3.1155.0 |

| [zod](https://github.com/colinhacks/zod) | 4.6.6 | 4.6.7 |

| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | 2.5.14 | 2.6.2 |

| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | 22.20.4 | 22.20.5 |

| [@aws-sdk/client-secrets-manager](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager) | 3.1142.0 | 3.1155.0 |

| [aws-cdk](https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk) | 2.1143.0 | 2.1146.0 |

| [aws-cdk-lib](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib) | 2.271.0 | 2.274.0 |

| [supertest](https://github.com/ladjs/supertest) | 7.3.0 | 7.3.1 |

| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | 5.0.3 | 5.0.5 |

| [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) | 6.41.0 | 6.42.1 |

| [react](https://github.com/react/react/tree/HEAD/packages/react) | 19.2.3 | 19.3.1 |

| [react-dom](https://github.com/react/react/tree/HEAD/packages/react-dom) | 19.2.3 | 19.3.1 |

| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | 8.3.4 | 8.3.5 |

Updates @aws-sdk/client-dynamodb from 3.1142.0 to 3.1155.0

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/releases">@​aws-sdk/client-dynamodb's releases</a>.</em></p>

<blockquote>

<h2>v3.1155.0</h2>

<h4>3.1155.0(2026-10-21)</h4>

<h5>Chores</h5>

<ul>

<li>temporarily disconnect from eclipse for Java formatting (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8375">#8375</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6d14aac795f8832dd2dd1e1512558f17c3414910">6d14aac7</a>)</li>

<li><strong>codegen:</strong> sync for JSON string serializer buffer fix and retryMode docs link (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8373">#8373</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276">5f53137d</a>)</li>

<li><strong>finspace:</strong> Remove finspace and finspace-data clients following the service shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8369">#8369</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/48e34c4812ab6850fe80c59efab282a2b6d73699">48e34c48</a>)</li>

<li><strong>tnb:</strong> Remove tnb clients following shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8370">#8370</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/e37bf8c2898e5e85201648f81dd07974e7d7e51c">e37bf8c2</a>)</li>

</ul>

<h5>New Features</h5>

<ul>

<li><strong>client-quicksight:</strong> Adds support for SharePoint and OneDrive two-legged OAuth certificate credentials and Google Workspace service account credentials when creating data sources (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0d47ac9e51ccff5e8d4a39220648e964c9a7e6b">d0d47ac9</a>)</li>

<li><strong>client-sfn:</strong> Release minor updates to API model (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6bb8593f440b172dd52eb92f05403edd91d28b4e">6bb8593f</a>)</li>

<li><strong>client-network-firewall:</strong> Adds support for Network Firewall Resolved IP validation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a6343601e54cdd8fba0f9e6f5125e819722c0de">6a634360</a>)</li>

<li><strong>client-datazone:</strong> Added custom designations support with new CRUD APIs. The designation field in project membership and policy grant APIs supports a new enum for custom designations. These APIs also support a new field for custom designation id. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/10021565d106f6d0beba65301a848c85de4e7b41">10021565</a>)</li>

<li><strong>client-ec2:</strong> Adds new response fields to DescribeInstanceStatus and Network Insights analysis results. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8e3796951062c3771c28ae881296628ae483d70b">8e379695</a>)</li>

<li><strong>client-lightsail:</strong> This release adds support for metrics related to system-disk performance. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d21dd9d963b0cfb5b7d502fdc71618f99498b451">d21dd9d9</a>)</li>

<li><strong>client-healthlake:</strong> Update the UpdateProfileWithAgent API to return a streaming response to provide more frequent updates on what the agent is doing. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c2730b304f9e2413e3a8bf24a88e1d829defaf43">c2730b30</a>)</li>

<li><strong>client-polly:</strong> Added support for the new voices - Kenneth (en-US), Nate (en-US), Tina (de-DE), Carlos (es-US), Carolina (pt-BR), Leo (pt-BR), Curtis (en-AU), Kiara (en-IN), Arjun (en-IN) and Hyunduk (ko-KR). They are available as a Generative voices only. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4494f473533076ef6ce315ed468028efe1eb717e">4494f473</a>)</li>

<li><strong>client-connect:</strong> Added support for AWS-managed security profiles. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/04f0c0b5b605a7e946574df2a8b75609c97ed012">04f0c0b5</a>)</li>

<li><strong>client-auto-scaling:</strong> EC2 Auto Scaling now supports account settings, letting you manage account-level configuration for Auto Scaling. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0cdb3960ad0f9178bbd3424f64a2f67bc4c981d">d0cdb396</a>)</li>

<li><strong>client-lex-models-v2:</strong> Adds support for Assisted NLU - Dialog Manager mode allowing usage of LLMs as the default NLU system and dialog management (<a href="https://github.com/aws/aws-sdk-js-v3/commit/671f2125f9e2b1a6391ed6617d38320526262a45">671f2125</a>)</li>

<li><strong>client-redshift-data:</strong> Add Redshift QueryUUID field to DescribeStatement response (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a328ab71b031e567f249eae1995cdc5f1d9d4d4">6a328ab7</a>)</li>

<li><strong>client-devops-agent:</strong> Adds support for Microsoft Teams as a notification service. Associations can now be created and updated with a Microsoft Teams team and channel configuration using the DevOps Agent API and SDKs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c5d8365175b93e38932d1aad1e07bed07a1b3641">c5d83651</a>)</li>

<li><strong>client-mediaconvert:</strong> Adds AV1 CBR rate control and scene change detection. New sliding window peak bitrate setting for all codecs. DASH adaptation set grouping update. Option to disable the AV1 perceptual quality filter. Support for vertical (portrait) AV1 encoding. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7e0a4261ef68fd7ece5dcdcf9c4a674ad4ab27d2">7e0a4261</a>)</li>

<li><strong>lib-dynamodb:</strong> expose transact write item types (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8334">#8334</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/2fdb917af4e8720bac65ef39c98ae350908d4744">2fdb917a</a>)</li>

<li><strong>dynamodb:</strong> add batch get item paginators for low level and document client (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8340">#8340</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8ec1336271054aa9c9e31233e53145b970e1164d">8ec13362</a>)</li>

<li><strong>lib-transfer-manager:</strong> add featureId tracking for TM (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8367">#8367</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/edb912d5b2f6ca25f82d6c7756a90bde04be5564">edb912d5</a>)</li>

</ul>

<hr />

<p>For list of updated packages, view <strong>updated-packages.md</strong> in <strong>assets-3.1155.0.zip</strong></p>

<h2>v3.1154.0</h2>

<h4>3.1154.0(2026-10-20)</h4>

<h5>New Features</h5>

<ul>

<li><strong>client-cloudwatchomni:</strong> Updating max value for maxResults in SearchPrincipals API (<a href="https://github.com/aws/aws-sdk-js-v3/commit/b0304f534e781e0a43966d89c797df9b4c0583d3">b0304f53</a>)</li>

<li><strong>client-rds:</strong> Amazon RDS now supports On-Demand Capacity Reservations for DB instances. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4a9c582bcbcf3c15de71e0557a07e01a91bcbf06">4a9c582b</a>)</li>

<li><strong>client-cloudwatch:</strong> Amazon CloudWatch now supports two new anomaly detector settings. AdaptationSpeed (FAST, NORMAL, SLOW) controls how fast the model adapts to baseline changes, and OutlierFilteringStrength (MINIMAL, MODERATE, STRICT) controls how aggressively outliers are filtered. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4ab3926140917afbd90a52fd3fb5b78d78e8fa27">4ab39261</a>)</li>

<li><strong>client-dynamodb:</strong> Adds support for disassociating a replica from an Amazon DynamoDB multi-Region eventual consistency global table, so you can keep it as a single-Region table with its existing data. Also adds disassociation protection, on by default, to help prevent accidental disassociation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/47fab49d153a3dab10e2b075ec437a421bc4f2a1">47fab49d</a>)</li>

<li><strong>client-bedrock:</strong> Amazon Bedrock Guardrails now supports a configurable tier for the contextual grounding policy via a new tier option. Select the Standard tier for grounding that better supports conversations and reasoning, with expanded language coverage. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7b180331b5f82144fbfe828d4bf59bdaa88c5997">7b180331</a>)</li>

<li><strong>client-ecs:</strong> ECS Service Gateway makes it easier for developers to deploy ECS services without having to worry about complex ingress networking constructs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/db0d1430a64c6455d0254f34837507f82d339dd6">db0d1430</a>)</li>

<li><strong>client-s3files:</strong> S3 Files adds support for the &quot;Misconfigured&quot; file system status. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/398f9d108747e8b9725b7d3ed9394d7c5a115334">398f9d10</a>)</li>

<li><strong>client-cleanrooms:</strong> This release allows customers and their partners to easily collaborate with data stored in Databricks, without having to move or share their underlying data among collaborators. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/0d7bcd99e437852b03f46307e84166866ae47e96">0d7bcd99</a>)</li>

<li><strong>client-workspaces-instances:</strong> Documentation update release for AWS service (<a href="https://github.com/aws/aws-sdk-js-v3/commit/9dc126403f7599980799add0eefcfbe599bdc883">9dc12640</a>)</li>

<li><strong>client-elasticache:</strong> LiveMigration enables customers to migrate from self-hosted EC2 Redis and Valkey clusters to ElastiCache Serverless with near-zero downtime. Customers control the migration through three API-driven phases (prepare, start, complete) that handle traffic proxying, data replication, and cutover. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/eefeb2a2599096fcddba9a9c85326da4fc23d2bc">eefeb2a2</a>)</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Changelog</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-dynamodb/CHANGELOG.md">@​aws-sdk/client-dynamodb's changelog</a>.</em></p>

<blockquote>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1154.0...v3.1155.0">3.1155.0</a> (2026-10-21)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1153.0...v3.1154.0">3.1154.0</a> (2026-10-20)</h1>

<h3>Features</h3>

<ul>

<li><strong>client-dynamodb:</strong> Adds support for disassociating a replica from an Amazon DynamoDB multi-Region eventual consistency global table, so you can keep it as a single-Region table with its existing data. Also adds disassociation protection, on by default, to help prevent accidental disassociation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/47fab49d153a3dab10e2b075ec437a421bc4f2a1">47fab49</a>)</li>

</ul>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1152.0...v3.1153.0">3.1153.0</a> (2026-10-19)</h1>

<h3>Features</h3>

<ul>

<li><strong>client-dynamodb:</strong> Enable account endpoint generation for existing CN and GovCloud regions (<a href="https://github.com/aws/aws-sdk-js-v3/commit/ca19aa35fd5555729bb74037015e8c97499cb642">ca19aa3</a>)</li>

</ul>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1151.0...v3.1152.0">3.1152.0</a> (2026-10-14)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1150.0...v3.1151.0">3.1151.0</a> (2026-10-13)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1149.0...v3.1150.0">3.1150.0</a> (2026-10-12)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-dynamodb</code></p>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/7c2f08900ba6f6ea424ac488694de80356541402"><code>7c2f089</code></a> Publish v3.1155.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276"><code>5f53137</code></a> chore(codegen): sync for JSON string serializer buffer fix and retryMode docs...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/f6ff312e2d31a54f8bfdef45a16604e4f42ff3f2"><code>f6ff312</code></a> Publish v3.1154.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/47fab49d153a3dab10e2b075ec437a421bc4f2a1"><code>47fab49</code></a> feat(client-dynamodb): Adds support for disassociating a replica from an Amaz...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/35085844c581d910f51deea1b2de48f6b4ffa704"><code>3508584</code></a> Publish v3.1153.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/ca19aa35fd5555729bb74037015e8c97499cb642"><code>ca19aa3</code></a> feat(client-dynamodb): Enable account endpoint generation for existing CN and...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3e350b59848e2bffcfe4d34a628e7adc136a6a55"><code>3e350b5</code></a> chore(codegen): sync for JSON codec and schema server plugin (<a href="https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-dynamodb/issues/8353">#8353</a>)</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3ce8aa778c22193dad5f7fcefe239e3a74a3cd4f"><code>3ce8aa7</code></a> Publish v3.1152.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/d6adfcb7baa396dd42060a74382b6aa2a1cbf0b5"><code>d6adfcb</code></a> Publish v3.1151.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/4c9a334a79b631cc110fb3a1d67695b4c07baf46"><code>4c9a334</code></a> Publish v3.1150.0</li>

<li>Additional commits viewable in <a href="https://github.com/aws/aws-sdk-js-v3/commits/v3.1155.0/clients/client-dynamodb">compare view</a></li>

</ul>

</details>

<br />

Updates @aws-sdk/lib-dynamodb from 3.1142.0 to 3.1155.0

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/releases">@​aws-sdk/lib-dynamodb's releases</a>.</em></p>

<blockquote>

<h2>v3.1155.0</h2>

<h4>3.1155.0(2026-10-21)</h4>

<h5>Chores</h5>

<ul>

<li>temporarily disconnect from eclipse for Java formatting (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8375">#8375</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6d14aac795f8832dd2dd1e1512558f17c3414910">6d14aac7</a>)</li>

<li><strong>codegen:</strong> sync for JSON string serializer buffer fix and retryMode docs link (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8373">#8373</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276">5f53137d</a>)</li>

<li><strong>finspace:</strong> Remove finspace and finspace-data clients following the service shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8369">#8369</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/48e34c4812ab6850fe80c59efab282a2b6d73699">48e34c48</a>)</li>

<li><strong>tnb:</strong> Remove tnb clients following shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8370">#8370</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/e37bf8c2898e5e85201648f81dd07974e7d7e51c">e37bf8c2</a>)</li>

</ul>

<h5>New Features</h5>

<ul>

<li><strong>client-quicksight:</strong> Adds support for SharePoint and OneDrive two-legged OAuth certificate credentials and Google Workspace service account credentials when creating data sources (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0d47ac9e51ccff5e8d4a39220648e964c9a7e6b">d0d47ac9</a>)</li>

<li><strong>client-sfn:</strong> Release minor updates to API model (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6bb8593f440b172dd52eb92f05403edd91d28b4e">6bb8593f</a>)</li>

<li><strong>client-network-firewall:</strong> Adds support for Network Firewall Resolved IP validation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a6343601e54cdd8fba0f9e6f5125e819722c0de">6a634360</a>)</li>

<li><strong>client-datazone:</strong> Added custom designations support with new CRUD APIs. The designation field in project membership and policy grant APIs supports a new enum for custom designations. These APIs also support a new field for custom designation id. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/10021565d106f6d0beba65301a848c85de4e7b41">10021565</a>)</li>

<li><strong>client-ec2:</strong> Adds new response fields to DescribeInstanceStatus and Network Insights analysis results. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8e3796951062c3771c28ae881296628ae483d70b">8e379695</a>)</li>

<li><strong>client-lightsail:</strong> This release adds support for metrics related to system-disk performance. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d21dd9d963b0cfb5b7d502fdc71618f99498b451">d21dd9d9</a>)</li>

<li><strong>client-healthlake:</strong> Update the UpdateProfileWithAgent API to return a streaming response to provide more frequent updates on what the agent is doing. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c2730b304f9e2413e3a8bf24a88e1d829defaf43">c2730b30</a>)</li>

<li><strong>client-polly:</strong> Added support for the new voices - Kenneth (en-US), Nate (en-US), Tina (de-DE), Carlos (es-US), Carolina (pt-BR), Leo (pt-BR), Curtis (en-AU), Kiara (en-IN), Arjun (en-IN) and Hyunduk (ko-KR). They are available as a Generative voices only. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4494f473533076ef6ce315ed468028efe1eb717e">4494f473</a>)</li>

<li><strong>client-connect:</strong> Added support for AWS-managed security profiles. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/04f0c0b5b605a7e946574df2a8b75609c97ed012">04f0c0b5</a>)</li>

<li><strong>client-auto-scaling:</strong> EC2 Auto Scaling now supports account settings, letting you manage account-level configuration for Auto Scaling. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0cdb3960ad0f9178bbd3424f64a2f67bc4c981d">d0cdb396</a>)</li>

<li><strong>client-lex-models-v2:</strong> Adds support for Assisted NLU - Dialog Manager mode allowing usage of LLMs as the default NLU system and dialog management (<a href="https://github.com/aws/aws-sdk-js-v3/commit/671f2125f9e2b1a6391ed6617d38320526262a45">671f2125</a>)</li>

<li><strong>client-redshift-data:</strong> Add Redshift QueryUUID field to DescribeStatement response (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a328ab71b031e567f249eae1995cdc5f1d9d4d4">6a328ab7</a>)</li>

<li><strong>client-devops-agent:</strong> Adds support for Microsoft Teams as a notification service. Associations can now be created and updated with a Microsoft Teams team and channel configuration using the DevOps Agent API and SDKs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c5d8365175b93e38932d1aad1e07bed07a1b3641">c5d83651</a>)</li>

<li><strong>client-mediaconvert:</strong> Adds AV1 CBR rate control and scene change detection. New sliding window peak bitrate setting for all codecs. DASH adaptation set grouping update. Option to disable the AV1 perceptual quality filter. Support for vertical (portrait) AV1 encoding. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7e0a4261ef68fd7ece5dcdcf9c4a674ad4ab27d2">7e0a4261</a>)</li>

<li><strong>lib-dynamodb:</strong> expose transact write item types (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8334">#8334</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/2fdb917af4e8720bac65ef39c98ae350908d4744">2fdb917a</a>)</li>

<li><strong>dynamodb:</strong> add batch get item paginators for low level and document client (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8340">#8340</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8ec1336271054aa9c9e31233e53145b970e1164d">8ec13362</a>)</li>

<li><strong>lib-transfer-manager:</strong> add featureId tracking for TM (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8367">#8367</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/edb912d5b2f6ca25f82d6c7756a90bde04be5564">edb912d5</a>)</li>

</ul>

<hr />

<p>For list of updated packages, view <strong>updated-packages.md</strong> in <strong>assets-3.1155.0.zip</strong></p>

<h2>v3.1154.0</h2>

<h4>3.1154.0(2026-10-20)</h4>

<h5>New Features</h5>

<ul>

<li><strong>client-cloudwatchomni:</strong> Updating max value for maxResults in SearchPrincipals API (<a href="https://github.com/aws/aws-sdk-js-v3/commit/b0304f534e781e0a43966d89c797df9b4c0583d3">b0304f53</a>)</li>

<li><strong>client-rds:</strong> Amazon RDS now supports On-Demand Capacity Reservations for DB instances. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4a9c582bcbcf3c15de71e0557a07e01a91bcbf06">4a9c582b</a>)</li>

<li><strong>client-cloudwatch:</strong> Amazon CloudWatch now supports two new anomaly detector settings. AdaptationSpeed (FAST, NORMAL, SLOW) controls how fast the model adapts to baseline changes, and OutlierFilteringStrength (MINIMAL, MODERATE, STRICT) controls how aggressively outliers are filtered. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4ab3926140917afbd90a52fd3fb5b78d78e8fa27">4ab39261</a>)</li>

<li><strong>client-dynamodb:</strong> Adds support for disassociating a replica from an Amazon DynamoDB multi-Region eventual consistency global table, so you can keep it as a single-Region table with its existing data. Also adds disassociation protection, on by default, to help prevent accidental disassociation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/47fab49d153a3dab10e2b075ec437a421bc4f2a1">47fab49d</a>)</li>

<li><strong>client-bedrock:</strong> Amazon Bedrock Guardrails now supports a configurable tier for the contextual grounding policy via a new tier option. Select the Standard tier for grounding that better supports conversations and reasoning, with expanded language coverage. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7b180331b5f82144fbfe828d4bf59bdaa88c5997">7b180331</a>)</li>

<li><strong>client-ecs:</strong> ECS Service Gateway makes it easier for developers to deploy ECS services without having to worry about complex ingress networking constructs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/db0d1430a64c6455d0254f34837507f82d339dd6">db0d1430</a>)</li>

<li><strong>client-s3files:</strong> S3 Files adds support for the &quot;Misconfigured&quot; file system status. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/398f9d108747e8b9725b7d3ed9394d7c5a115334">398f9d10</a>)</li>

<li><strong>client-cleanrooms:</strong> This release allows customers and their partners to easily collaborate with data stored in Databricks, without having to move or share their underlying data among collaborators. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/0d7bcd99e437852b03f46307e84166866ae47e96">0d7bcd99</a>)</li>

<li><strong>client-workspaces-instances:</strong> Documentation update release for AWS service (<a href="https://github.com/aws/aws-sdk-js-v3/commit/9dc126403f7599980799add0eefcfbe599bdc883">9dc12640</a>)</li>

<li><strong>client-elasticache:</strong> LiveMigration enables customers to migrate from self-hosted EC2 Redis and Valkey clusters to ElastiCache Serverless with near-zero downtime. Customers control the migration through three API-driven phases (prepare, start, complete) that handle traffic proxying, data replication, and cutover. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/eefeb2a2599096fcddba9a9c85326da4fc23d2bc">eefeb2a2</a>)</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Changelog</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/blob/main/lib/lib-dynamodb/CHANGELOG.md">@​aws-sdk/lib-dynamodb's changelog</a>.</em></p>

<blockquote>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1154.0...v3.1155.0">3.1155.0</a> (2026-10-21)</h1>

<h3>Features</h3>

<ul>

<li><strong>dynamodb:</strong> add batch get item paginators for low level and document client (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/issues/8340">#8340</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8ec1336271054aa9c9e31233e53145b970e1164d">8ec1336</a>)</li>

<li><strong>lib-dynamodb:</strong> expose transact write item types (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/issues/8334">#8334</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/2fdb917af4e8720bac65ef39c98ae350908d4744">2fdb917</a>)</li>

</ul>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1153.0...v3.1154.0">3.1154.0</a> (2026-10-20)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/lib-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1152.0...v3.1153.0">3.1153.0</a> (2026-10-19)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/lib-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1151.0...v3.1152.0">3.1152.0</a> (2026-10-14)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/lib-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1150.0...v3.1151.0">3.1151.0</a> (2026-10-13)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/lib-dynamodb</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1149.0...v3.1150.0">3.1150.0</a> (2026-10-12)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/lib-dynamodb</code></p>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/7c2f08900ba6f6ea424ac488694de80356541402"><code>7c2f089</code></a> Publish v3.1155.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276"><code>5f53137</code></a> chore(codegen): sync for JSON string serializer buffer fix and retryMode docs...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/2fdb917af4e8720bac65ef39c98ae350908d4744"><code>2fdb917</code></a> feat(lib-dynamodb): expose transact write item types (<a href="https://github.com/aws/aws-sdk-js-v3/tree/HEAD/lib/lib-dynamodb/issues/8334">#8334</a>)</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/8ec1336271054aa9c9e31233e53145b970e1164d"><code>8ec1336</code></a> feat(dynamodb): add batch get item paginators for low level and document clie...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/f6ff312e2d31a54f8bfdef45a16604e4f42ff3f2"><code>f6ff312</code></a> Publish v3.1154.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/35085844c581d910f51deea1b2de48f6b4ffa704"><code>3508584</code></a> Publish v3.1153.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3e350b59848e2bffcfe4d34a628e7adc136a6a55"><code>3e350b5</code></a> chore(codegen): sync for JSON codec and schema server plugin (<a href="https://github.com/aws/aws-sdk-js-v3/tree/HEAD/lib/lib-dynamodb/issues/8353">#8353</a>)</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3ce8aa778c22193dad5f7fcefe239e3a74a3cd4f"><code>3ce8aa7</code></a> Publish v3.1152.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/d6adfcb7baa396dd42060a74382b6aa2a1cbf0b5"><code>d6adfcb</code></a> Publish v3.1151.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/4c9a334a79b631cc110fb3a1d67695b4c07baf46"><code>4c9a334</code></a> Publish v3.1150.0</li>

<li>Additional commits viewable in <a href="https://github.com/aws/aws-sdk-js-v3/commits/v3.1155.0/lib/lib-dynamodb">compare view</a></li>

</ul>

</details>

<br />

Updates zod from 4.6.6 to 4.6.7

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/colinhacks/zod/releases">zod's releases</a>.</em></p>

<blockquote>

<h2>v4.6.7</h2>

<h2>Commits:</h2>

<ul>

<li>b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7</li>

</ul>

</blockquote>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/colinhacks/zod/commit/b500a2ee95134f81d74da7911d7378dd2853d042"><code>b500a2e</code></a> 4.6.7</li>

<li>See full diff in <a href="https://github.com/colinhacks/zod/compare/v4.6.6...v4.6.7">compare view</a></li>

</ul>

</details>

<br />

Updates @biomejs/biome from 2.5.14 to 2.6.2

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/biomejs/biome/releases">@​biomejs/biome's releases</a>.</em></p>

<blockquote>

<h2>Biome CLI v2.6.2</h2>

<h2>2.6.2</h2>

<h3>Minor Changes</h3>

<ul>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11479">#11479</a> <a href="https://github.com/biomejs/biome/commit/5c60ba83b6bb2442eb3d6157b328719d0c39a5c2"><code>5c60ba8</code></a> Thanks <a href="https://github.com/nhedger"><code>@​nhedger</code></a>! - Added a <code>--git</code> flag to <code>biome init</code>. The flag enables Git VCS integration and sets <code>vcs.useIgnoreFile</code> to <code>true</code> in the generated configuration, even when the command runs outside a Git repository.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11742">#11742</a> <a href="https://github.com/biomejs/biome/commit/3a1356d089ee0e99c7a1c9f20df7785efe3f11b4"><code>3a1356d</code></a> Thanks <a href="https://github.com/Netail"><code>@​Netail</code></a>! - Added the <code>biome migrate stylelint</code> command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass <code>--write</code> to apply the changes, and <code>--include-inspired</code> or <code>--include-nursery</code> to migrate additional rules.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/12318">#12318</a> <a href="https://github.com/biomejs/biome/commit/774b5b573259745d7b6a8545d39eed20f1620421"><code>774b5b5</code></a> Thanks <a href="https://github.com/Netail"><code>@​Netail</code></a>! - Added the new assist action <a href="https://biomejs.dev/assist/actions/use-graphql-sorted-definitions/"><code>useGraphqlSortedDefinitions</code></a>, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.</p>

<p><strong>Invalid</strong>:</p>

<pre lang="graphql"><code>type User {

id: ID!

}

<p>enum Role {<br />

ADMIN<br />

USER<br />

}</p>

<p>directive <a href="https://github.com/auth"><code>@​auth</code></a> on FIELD_DEFINITION<br />

</code></pre></p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/6886">#6886</a> <a href="https://github.com/biomejs/biome/commit/3479d1583a888e2d393b32129616c7327af7c320"><code>3479d15</code></a> Thanks <a href="https://github.com/christymcgrory"><code>@​christymcgrory</code></a>! - <code>biome rage</code> now shows the resolved <code>files.includes</code> and <code>files.ignoreUnknown</code> configuration.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11102">#11102</a> <a href="https://github.com/biomejs/biome/commit/0874b7f87a17474029763988c0c1f17812298441"><code>0874b7f</code></a> Thanks <a href="https://github.com/gameroman"><code>@​gameroman</code></a>! - Added support for <a href="https://biomejs.dev/linter/rules/use-tailwind-sorted-classes/"><code>useTailwindSortedClasses</code></a> rule in HTML-ish files.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/10711">#10711</a> <a href="https://github.com/biomejs/biome/commit/40de5a0383473d37a4667f7cdb46817e0e73b686"><code>40de5a0</code></a> Thanks <a href="https://github.com/soconnor-seeq"><code>@​soconnor-seeq</code></a>! - Adds a new <code>resolutionKind</code> option for object-syntax plugin entries.</p>

<p>This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.</p>

<pre lang="json"><code>{

&quot;plugins&quot;: [

{ &quot;path&quot;: &quot;./grit/no-debugger.grit&quot;, &quot;resolutionKind&quot;: &quot;config&quot; },

{ &quot;path&quot;: &quot;local-plugin.grit&quot;, &quot;resolutionKind&quot;: &quot;project&quot; },

{ &quot;path&quot;: &quot;local-plugin.grit&quot; }

]

}

</code></pre>

<p>Use <code>resolutionKind: &quot;config&quot;</code> to resolve the plugin from the configuration file that declares it. Use <code>resolutionKind: &quot;project&quot;</code> to resolve the plugin from the consuming project. When omitted, <code>resolutionKind</code> defaults to <code>project</code>. This only affects plugin resolution; <code>includes</code> still apply to end-user project files as usual.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11432">#11432</a> <a href="https://github.com/biomejs/biome/commit/4befd08057836e6d3881c768bf7a49e5820a7352"><code>4befd08</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Added <code>biome inspect config</code> to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.</p>

<p>Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.</p>

</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Changelog</summary>

<p><em>Sourced from <a href="https://github.com/biomejs/biome/blob/@biomejs/biome@2.6.2/packages/@biomejs/biome/CHANGELOG.md">@​biomejs/biome's changelog</a>.</em></p>

<blockquote>

<h2>2.6.2</h2>

<h3>Patch Changes</h3>

<ul>

<li><a href="https://redirect.github.com/biomejs/biome/pull/12494">#12494</a> <a href="https://github.com/biomejs/biome/commit/3f4043029bf5db0916b2d302b5797cca4927e178"><code>3f40430</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Fix another patch</li>

</ul>

<h2>2.6.1</h2>

<h3>Patch Changes</h3>

<ul>

<li><a href="https://redirect.github.com/biomejs/biome/pull/12492">#12492</a> <a href="https://github.com/biomejs/biome/commit/edaa1db68abbef94d9605bc6de0246a1fcab52e1"><code>edaa1db</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Fixes a problem with npm publishing</li>

</ul>

<h2>2.6.0</h2>

<h3>Minor Changes</h3>

<ul>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11479">#11479</a> <a href="https://github.com/biomejs/biome/commit/5c60ba83b6bb2442eb3d6157b328719d0c39a5c2"><code>5c60ba8</code></a> Thanks <a href="https://github.com/nhedger"><code>@​nhedger</code></a>! - Added a <code>--git</code> flag to <code>biome init</code>. The flag enables Git VCS integration and sets <code>vcs.useIgnoreFile</code> to <code>true</code> in the generated configuration, even when the command runs outside a Git repository.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11742">#11742</a> <a href="https://github.com/biomejs/biome/commit/3a1356d089ee0e99c7a1c9f20df7785efe3f11b4"><code>3a1356d</code></a> Thanks <a href="https://github.com/Netail"><code>@​Netail</code></a>! - Added the <code>biome migrate stylelint</code> command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass <code>--write</code> to apply the changes, and <code>--include-inspired</code> or <code>--include-nursery</code> to migrate additional rules.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/12318">#12318</a> <a href="https://github.com/biomejs/biome/commit/774b5b573259745d7b6a8545d39eed20f1620421"><code>774b5b5</code></a> Thanks <a href="https://github.com/Netail"><code>@​Netail</code></a>! - Added the new assist action <a href="https://biomejs.dev/assist/actions/use-graphql-sorted-definitions/"><code>useGraphqlSortedDefinitions</code></a>, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.</p>

<p><strong>Invalid</strong>:</p>

<pre lang="graphql"><code>type User {

id: ID!

}

<p>enum Role {<br />

ADMIN<br />

USER<br />

}</p>

<p>directive <a href="https://github.com/auth"><code>@​auth</code></a> on FIELD_DEFINITION<br />

</code></pre></p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/6886">#6886</a> <a href="https://github.com/biomejs/biome/commit/3479d1583a888e2d393b32129616c7327af7c320"><code>3479d15</code></a> Thanks <a href="https://github.com/christymcgrory"><code>@​christymcgrory</code></a>! - <code>biome rage</code> now shows the resolved <code>files.includes</code> and <code>files.ignoreUnknown</code> configuration.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/11102">#11102</a> <a href="https://github.com/biomejs/biome/commit/0874b7f87a17474029763988c0c1f17812298441"><code>0874b7f</code></a> Thanks <a href="https://github.com/gameroman"><code>@​gameroman</code></a>! - Added support for <a href="https://biomejs.dev/linter/rules/use-tailwind-sorted-classes/"><code>useTailwindSortedClasses</code></a> rule in HTML-ish files.</p>

</li>

<li>

<p><a href="https://redirect.github.com/biomejs/biome/pull/10711">#10711</a> <a href="https://github.com/biomejs/biome/commit/40de5a0383473d37a4667f7cdb46817e0e73b686"><code>40de5a0</code></a> Thanks <a href="https://github.com/soconnor-seeq"><code>@​soconnor-seeq</code></a>! - Adds a new <code>resolutionKind</code> option for object-syntax plugin entries.</p>

<p>This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.</p>

<pre lang="json"><code>{

&quot;plugins&quot;: [

{ &quot;path&quot;: &quot;./grit/no-debugger.grit&quot;, &quot;resolutionKind&quot;: &quot;config&quot; },

{ &quot;path&quot;: &quot;local-plugin.grit&quot;, &quot;resolutionKind&quot;: &quot;project&quot; },

</code></pre>

</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/biomejs/biome/commit/0d9aef6a5adf794118be3b9920189b33a413dd96"><code>0d9aef6</code></a> ci: release (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12495">#12495</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/30ffad1461051d595210f7fabcd67813942ebee4"><code>30ffad1</code></a> ci: release (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12493">#12493</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/8c814e1b2c8f1c11acd3aed143f5c078beab4f78"><code>8c814e1</code></a> ci: release (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12065">#12065</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/e51cec2bc6fb041afbd4dc17269c4d0fb0fbbc18"><code>e51cec2</code></a> chore: update sponsors (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12428">#12428</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/cb88f072f66f90c478908fcb42786ea9b6b30851"><code>cb88f07</code></a> feat(lint): add noSvelteClassDirective (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12254">#12254</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/774b5b573259745d7b6a8545d39eed20f1620421"><code>774b5b5</code></a> feat: sorted GraphQL documents (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12318">#12318</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/914dca7beb9befb489e1d833469bd0f565388935"><code>914dca7</code></a> feat(lint/js): add noUselessCall (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12082">#12082</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/a3fa0d6526e5ce6ab3b0c87fb74813ecdef0b2bd"><code>a3fa0d6</code></a> feat(graphql_analyze): implement useSortedArguments (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12282">#12282</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/5f8ea6cc9a75f666e5f8cba2f7fb5aa6b13d8da5"><code>5f8ea6c</code></a> feat(lint): add noVueLifecycleAfterAwait (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12229">#12229</a>)</li>

<li><a href="https://github.com/biomejs/biome/commit/b92638b40689c7714fe3d84db06a7a62110f796d"><code>b92638b</code></a> feat(lint): add noVueShadowNativeEvents (<a href="https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome/issues/12136">#12136</a>)</li>

<li>Additional commits viewable in <a href="https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.2/packages/@biomejs/biome">compare view</a></li>

</ul>

</details>

<br />

Updates @types/node from 22.20.4 to 22.20.5

<details>

<summary>Commits</summary>

<ul>

<li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li>

</ul>

</details>

<br />

Updates @aws-sdk/client-secrets-manager from 3.1142.0 to 3.1155.0

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/releases">@​aws-sdk/client-secrets-manager's releases</a>.</em></p>

<blockquote>

<h2>v3.1155.0</h2>

<h4>3.1155.0(2026-10-21)</h4>

<h5>Chores</h5>

<ul>

<li>temporarily disconnect from eclipse for Java formatting (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8375">#8375</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6d14aac795f8832dd2dd1e1512558f17c3414910">6d14aac7</a>)</li>

<li><strong>codegen:</strong> sync for JSON string serializer buffer fix and retryMode docs link (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8373">#8373</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276">5f53137d</a>)</li>

<li><strong>finspace:</strong> Remove finspace and finspace-data clients following the service shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8369">#8369</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/48e34c4812ab6850fe80c59efab282a2b6d73699">48e34c48</a>)</li>

<li><strong>tnb:</strong> Remove tnb clients following shutdown (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8370">#8370</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/e37bf8c2898e5e85201648f81dd07974e7d7e51c">e37bf8c2</a>)</li>

</ul>

<h5>New Features</h5>

<ul>

<li><strong>client-quicksight:</strong> Adds support for SharePoint and OneDrive two-legged OAuth certificate credentials and Google Workspace service account credentials when creating data sources (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0d47ac9e51ccff5e8d4a39220648e964c9a7e6b">d0d47ac9</a>)</li>

<li><strong>client-sfn:</strong> Release minor updates to API model (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6bb8593f440b172dd52eb92f05403edd91d28b4e">6bb8593f</a>)</li>

<li><strong>client-network-firewall:</strong> Adds support for Network Firewall Resolved IP validation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a6343601e54cdd8fba0f9e6f5125e819722c0de">6a634360</a>)</li>

<li><strong>client-datazone:</strong> Added custom designations support with new CRUD APIs. The designation field in project membership and policy grant APIs supports a new enum for custom designations. These APIs also support a new field for custom designation id. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/10021565d106f6d0beba65301a848c85de4e7b41">10021565</a>)</li>

<li><strong>client-ec2:</strong> Adds new response fields to DescribeInstanceStatus and Network Insights analysis results. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8e3796951062c3771c28ae881296628ae483d70b">8e379695</a>)</li>

<li><strong>client-lightsail:</strong> This release adds support for metrics related to system-disk performance. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d21dd9d963b0cfb5b7d502fdc71618f99498b451">d21dd9d9</a>)</li>

<li><strong>client-healthlake:</strong> Update the UpdateProfileWithAgent API to return a streaming response to provide more frequent updates on what the agent is doing. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c2730b304f9e2413e3a8bf24a88e1d829defaf43">c2730b30</a>)</li>

<li><strong>client-polly:</strong> Added support for the new voices - Kenneth (en-US), Nate (en-US), Tina (de-DE), Carlos (es-US), Carolina (pt-BR), Leo (pt-BR), Curtis (en-AU), Kiara (en-IN), Arjun (en-IN) and Hyunduk (ko-KR). They are available as a Generative voices only. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4494f473533076ef6ce315ed468028efe1eb717e">4494f473</a>)</li>

<li><strong>client-connect:</strong> Added support for AWS-managed security profiles. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/04f0c0b5b605a7e946574df2a8b75609c97ed012">04f0c0b5</a>)</li>

<li><strong>client-auto-scaling:</strong> EC2 Auto Scaling now supports account settings, letting you manage account-level configuration for Auto Scaling. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/d0cdb3960ad0f9178bbd3424f64a2f67bc4c981d">d0cdb396</a>)</li>

<li><strong>client-lex-models-v2:</strong> Adds support for Assisted NLU - Dialog Manager mode allowing usage of LLMs as the default NLU system and dialog management (<a href="https://github.com/aws/aws-sdk-js-v3/commit/671f2125f9e2b1a6391ed6617d38320526262a45">671f2125</a>)</li>

<li><strong>client-redshift-data:</strong> Add Redshift QueryUUID field to DescribeStatement response (<a href="https://github.com/aws/aws-sdk-js-v3/commit/6a328ab71b031e567f249eae1995cdc5f1d9d4d4">6a328ab7</a>)</li>

<li><strong>client-devops-agent:</strong> Adds support for Microsoft Teams as a notification service. Associations can now be created and updated with a Microsoft Teams team and channel configuration using the DevOps Agent API and SDKs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/c5d8365175b93e38932d1aad1e07bed07a1b3641">c5d83651</a>)</li>

<li><strong>client-mediaconvert:</strong> Adds AV1 CBR rate control and scene change detection. New sliding window peak bitrate setting for all codecs. DASH adaptation set grouping update. Option to disable the AV1 perceptual quality filter. Support for vertical (portrait) AV1 encoding. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7e0a4261ef68fd7ece5dcdcf9c4a674ad4ab27d2">7e0a4261</a>)</li>

<li><strong>lib-dynamodb:</strong> expose transact write item types (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8334">#8334</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/2fdb917af4e8720bac65ef39c98ae350908d4744">2fdb917a</a>)</li>

<li><strong>dynamodb:</strong> add batch get item paginators for low level and document client (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8340">#8340</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/8ec1336271054aa9c9e31233e53145b970e1164d">8ec13362</a>)</li>

<li><strong>lib-transfer-manager:</strong> add featureId tracking for TM (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/8367">#8367</a>) (<a href="https://github.com/aws/aws-sdk-js-v3/commit/edb912d5b2f6ca25f82d6c7756a90bde04be5564">edb912d5</a>)</li>

</ul>

<hr />

<p>For list of updated packages, view <strong>updated-packages.md</strong> in <strong>assets-3.1155.0.zip</strong></p>

<h2>v3.1154.0</h2>

<h4>3.1154.0(2026-10-20)</h4>

<h5>New Features</h5>

<ul>

<li><strong>client-cloudwatchomni:</strong> Updating max value for maxResults in SearchPrincipals API (<a href="https://github.com/aws/aws-sdk-js-v3/commit/b0304f534e781e0a43966d89c797df9b4c0583d3">b0304f53</a>)</li>

<li><strong>client-rds:</strong> Amazon RDS now supports On-Demand Capacity Reservations for DB instances. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4a9c582bcbcf3c15de71e0557a07e01a91bcbf06">4a9c582b</a>)</li>

<li><strong>client-cloudwatch:</strong> Amazon CloudWatch now supports two new anomaly detector settings. AdaptationSpeed (FAST, NORMAL, SLOW) controls how fast the model adapts to baseline changes, and OutlierFilteringStrength (MINIMAL, MODERATE, STRICT) controls how aggressively outliers are filtered. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/4ab3926140917afbd90a52fd3fb5b78d78e8fa27">4ab39261</a>)</li>

<li><strong>client-dynamodb:</strong> Adds support for disassociating a replica from an Amazon DynamoDB multi-Region eventual consistency global table, so you can keep it as a single-Region table with its existing data. Also adds disassociation protection, on by default, to help prevent accidental disassociation. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/47fab49d153a3dab10e2b075ec437a421bc4f2a1">47fab49d</a>)</li>

<li><strong>client-bedrock:</strong> Amazon Bedrock Guardrails now supports a configurable tier for the contextual grounding policy via a new tier option. Select the Standard tier for grounding that better supports conversations and reasoning, with expanded language coverage. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/7b180331b5f82144fbfe828d4bf59bdaa88c5997">7b180331</a>)</li>

<li><strong>client-ecs:</strong> ECS Service Gateway makes it easier for developers to deploy ECS services without having to worry about complex ingress networking constructs. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/db0d1430a64c6455d0254f34837507f82d339dd6">db0d1430</a>)</li>

<li><strong>client-s3files:</strong> S3 Files adds support for the &quot;Misconfigured&quot; file system status. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/398f9d108747e8b9725b7d3ed9394d7c5a115334">398f9d10</a>)</li>

<li><strong>client-cleanrooms:</strong> This release allows customers and their partners to easily collaborate with data stored in Databricks, without having to move or share their underlying data among collaborators. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/0d7bcd99e437852b03f46307e84166866ae47e96">0d7bcd99</a>)</li>

<li><strong>client-workspaces-instances:</strong> Documentation update release for AWS service (<a href="https://github.com/aws/aws-sdk-js-v3/commit/9dc126403f7599980799add0eefcfbe599bdc883">9dc12640</a>)</li>

<li><strong>client-elasticache:</strong> LiveMigration enables customers to migrate from self-hosted EC2 Redis and Valkey clusters to ElastiCache Serverless with near-zero downtime. Customers control the migration through three API-driven phases (prepare, start, complete) that handle traffic proxying, data replication, and cutover. (<a href="https://github.com/aws/aws-sdk-js-v3/commit/eefeb2a2599096fcddba9a9c85326da4fc23d2bc">eefeb2a2</a>)</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Changelog</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-secrets-manager/CHANGELOG.md">@​aws-sdk/client-secrets-manager's changelog</a>.</em></p>

<blockquote>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1154.0...v3.1155.0">3.1155.0</a> (2026-10-21)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1153.0...v3.1154.0">3.1154.0</a> (2026-10-20)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1152.0...v3.1153.0">3.1153.0</a> (2026-10-19)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1151.0...v3.1152.0">3.1152.0</a> (2026-10-14)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1150.0...v3.1151.0">3.1151.0</a> (2026-10-13)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1149.0...v3.1150.0">3.1150.0</a> (2026-10-12)</h1>

<p><strong>Note:</strong> Version bump only for package <code>@​aws-sdk/client-secrets-manager</code></p>

<h1><a href="https://github.com/aws/aws-sdk-js-v3/compare/v3.1148.0...v3.1149.0">3.1149.0</a> (2026-10-09)</h1>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/7c2f08900ba6f6ea424ac488694de80356541402"><code>7c2f089</code></a> Publish v3.1155.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/5f53137d303161693250579a6a6dd3c501655276"><code>5f53137</code></a> chore(codegen): sync for JSON string serializer buffer fix and retryMode docs...</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/f6ff312e2d31a54f8bfdef45a16604e4f42ff3f2"><code>f6ff312</code></a> Publish v3.1154.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/35085844c581d910f51deea1b2de48f6b4ffa704"><code>3508584</code></a> Publish v3.1153.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3e350b59848e2bffcfe4d34a628e7adc136a6a55"><code>3e350b5</code></a> chore(codegen): sync for JSON codec and schema server plugin (<a href="https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager/issues/8353">#8353</a>)</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/3ce8aa778c22193dad5f7fcefe239e3a74a3cd4f"><code>3ce8aa7</code></a> Publish v3.1152.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/d6adfcb7baa396dd42060a74382b6aa2a1cbf0b5"><code>d6adfcb</code></a> Publish v3.1151.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/4c9a334a79b631cc110fb3a1d67695b4c07baf46"><code>4c9a334</code></a> Publish v3.1150.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/a960c14e8ce09ab8fd09352e40d75c6b9d52c1ca"><code>a960c14</code></a> Publish v3.1149.0</li>

<li><a href="https://github.com/aws/aws-sdk-js-v3/commit/5773a7515472dbdf2760c61e4a462b71800c50e7"><code>5773a75</code></a> chore(codegen): sync for endpoint cache fix and pre-schema error fallback (<a href="https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager/issues/8">#8</a>...</li>

<li>Additional commits viewable in <a href="https://github.com/aws/aws-sdk-js-v3/commits/v3.1155.0/clients/client-secrets-manager">compare view</a></li>

</ul>

</details>

<br />

Updates aws-cdk from 2.1143.0 to 2.1146.0

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/aws/aws-cdk-cli/releases">aws-cdk's releases</a>.</em></p>

<blockquote>

<h2>aws-cdk@v2.1146.0</h2>

<h2><a href="https://github.com/aws/aws-cdk-cli/compare/aws-cdk@v2.1145.0...aws-cdk@v2.1146.0">2.1146.0</a> (2026-10-20)</h2>

<h3>Features</h3>

<ul>

<li><strong>deps:</strong> upgrade aws-cdk-lib (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2038">#2038</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/01e711bd5c8dd939f235d922f555ede41bc574f1">01e711b</a>)</li>

<li><strong>toolkit-lib:</strong> support CloudFormation rollback triggers (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1881">#1881</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/133dfa467eb69b3317e8fbfffe4b275d512c2d95">133dfa4</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/5170">aws/aws-cdk#5170</a></li>

</ul>

<h3>Bug Fixes</h3>

<ul>

<li><strong>cli:</strong> pass CloudFormation parameters to diff change sets (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2030">#2030</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/d27b445e169074eb8af01b681b41c70eec31836a">d27b445</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1995">#1995</a></li>

<li><strong>toolkit-lib:</strong> change-set diff hides an added key in a JSON string with an intrinsic (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2042">#2042</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/1b0155a046ef50f1f124a084326ee8bb75342907">1b0155a</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2036">#2036</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2045">#2045</a>, references <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1668">#1668</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/641">#641</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1951">#1951</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1668">#1668</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1951">#1951</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1785">#1785</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/641">#641</a></li>

<li><strong>toolkit-lib:</strong> commands fail when deployed template has duplicate keys (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2044">#2044</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/9091cb560006b9266c7c6bf536adc06cb0d24e26">9091cb5</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1911">#1911</a>, references <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2043">#2043</a></li>

<li><strong>toolkit-lib:</strong> region lookup ignores AWS_EC2_METADATA_DISABLED (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2049">#2049</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/60e0a2d936ef1b5e688064ed7be35b36b0eff33a">60e0a2d</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2061">#2061</a></li>

<li><strong>toolkit-lib:</strong> restore the replacement guard when rollback is disabled (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2041">#2041</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/0b4f9eb22bb115e6120a6f409a149d02505384d6">0b4f9eb</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1931">#1931</a></li>

</ul>

<h2>aws-cdk@v2.1145.0</h2>

<h2><a href="https://github.com/aws/aws-cdk-cli/compare/aws-cdk@v2.1144.0...aws-cdk@v2.1145.0">2.1145.0</a> (2026-10-08)</h2>

<h3>Features</h3>

<ul>

<li><strong>cli:</strong> add <code>--fail-on</code> to <code>cdk diff</code> (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2020">#2020</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/fba21bbf3650ef10ef828b29df51d31bf86a9966">fba21bb</a>), references <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2010">#2010</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2011">#2011</a></li>

<li><strong>cli:</strong> add <code>destructive</code> to <code>cdk deploy --require-approval</code> (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2021">#2021</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/4b8744e761dcd04d6b8b0852d23806b1ade5f3f4">4b8744e</a>), references <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2010">#2010</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2011">#2011</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2020">#2020</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2011">#2011</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2011">#2011</a></li>

<li><strong>cli:</strong> add <code>destructive</code> to <code>cdk diff --fail-on</code> (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2011">#2011</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/a98947fad946e98a311a0dc6b983cf27b6dd823e">a98947f</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2010">#2010</a></li>

<li><strong>deps:</strong> upgrade aws-cdk-lib (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2009">#2009</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/32f9b4ae5f24048ea6f4a37f99c504d81bb077cb">32f9b4a</a>)</li>

<li>move validation report handling code into cloud-assembly-api (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2004">#2004</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/d673ac1972b2a71a6adb43d5517adb2dec3e633e">d673ac1</a>)</li>

</ul>

<h3>Bug Fixes</h3>

<ul>

<li><strong>aws-cdk:</strong> reject migrate filters with stack and path sources (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2017">#2017</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/2f60b35d28c167d48ed99d38459037fef7c7aef5">2f60b35</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1571">#1571</a></li>

<li><strong>cli:</strong> respect stack outputs in cdk watch (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2023">#2023</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/59c3a70229ea2842451a04a262269b81f1d2012d">59c3a70</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1649">#1649</a></li>

<li><strong>cli:</strong> unchanged stacks are not skipped on the change-set method (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2014">#2014</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/d9696a441e5e64fe039f3e9aaa20272538e77cd6">d9696a4</a>), closes <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2013">#2013</a>, references <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1273">#1273</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1273">#1273</a> <a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1387">#1387</a></li>

</ul>

<h2>aws-cdk@v2.1144.0</h2>

<h2><a href="https://github.com/aws/aws-cdk-cli/compare/aws-cdk@v2.1143.0...aws-cdk@v2.1144.0">2.1144.0</a> (2026-09-30)</h2>

<h3>Features</h3>

<ul>

<li><strong>cli:</strong> send telemetry from a detached subprocess to unblock CLI exit (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/1779">#1779</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/c5d39583e4d4c6d4a6fb793fbeedbd2937c7f49f">c5d3958</a>)</li>

<li><strong>deps:</strong> upgrade aws-cdk-lib (<a href="https://redirect.github.com/aws/aws-cdk-cli/issues/2000">#2000</a>) (<a href="https://github.com/aws/aws-cdk-cli/commit/ff8add046dc54119da7ac21c461bbb94c507bbd4">ff8add0</a>)</li>

</ul>

</blockquote>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/60e0a2d936ef1b5e688064ed7be35b36b0eff33a"><code>60e0a2d</code></a> fix(toolkit-lib): region lookup ignores AWS_EC2_METADATA_DISABLED (<a href="https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk/issues/2049">#2049</a>)</li>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/2e67f1282a28d32ad2b9d8fa46d0a7cce6a82523"><code>2e67f12</code></a> chore(deps): upgrade dependencies (<a href="https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk/issues/2052">#2052</a>)</li>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/1b0155a046ef50f1f124a084326ee8bb75342907"><code>1b0155a</code></a> fix(toolkit-lib): change-set diff hides an added key in a JSON string with an...</li>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/0b4f9eb22bb115e6120a6f409a149d02505384d6"><code>0b4f9eb</code></a> fix(toolkit-lib): restore the replacement guard when rollback is disabled (<a href="https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk/issues/2">#2</a>...</li>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/9091cb560006b9266c7c6bf536adc06cb0d24e26"><code>9091cb5</code></a> fix(toolkit-lib): commands fail when deployed template has duplicate keys (<a href="https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk/issues/2">#2</a>...</li>

<li><a href="https://github.com/aws/aws-cdk-cli/commit/d27b445e169074eb8af01b681b41c70eec31836a"><code>...

_Description has been truncated_

#18 — chore(deps): Bump actions/setup-node from 7.0.0 to 7.1.0 in the actions group across 1 directory @dependabot[bot]  dependenciesgithub_actions

Bumps the actions group with 1 update in the / directory: [actions/setup-node](https://github.com/actions/setup-node).

Updates actions/setup-node from 7.0.0 to 7.1.0

<details>

<summary>Release notes</summary>

<p><em>Sourced from <a href="https://github.com/actions/setup-node/releases">actions/setup-node's releases</a>.</em></p>

<blockquote>

<h2>v7.1.0</h2>

<h2>What's Changed</h2>

<h3>Enhancements:</h3>

<ul>

<li>Add support for mise.toml file by <a href="https://github.com/gperdomor"><code>@​gperdomor</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1421">actions/setup-node#1421</a></li>

<li>Support absolute paths in node-version-file by <a href="https://github.com/v-mahabaleshwars"><code>@​v-mahabaleshwars</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1633">actions/setup-node#1633</a></li>

</ul>

<h3>Bug fixes:</h3>

<ul>

<li>Add Node version validation and manifest fetch retry by <a href="https://github.com/v-jitenderpalsingh"><code>@​v-jitenderpalsingh</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1580">actions/setup-node#1580</a></li>

</ul>

<h3>Documentation updates:</h3>

<ul>

<li>README.md: bump actions/checkout to latest version 7 by <a href="https://github.com/deining"><code>@​deining</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1578">actions/setup-node#1578</a></li>

<li>docs: add V7 ESM migration and NODE_AUTH_TOKEN behavior change by <a href="https://github.com/v-gowridurgad"><code>@​v-gowridurgad</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1593">actions/setup-node#1593</a></li>

<li>Fixed cache recommendation syntax by <a href="https://github.com/SubJunk"><code>@​SubJunk</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1603">actions/setup-node#1603</a></li>

</ul>

<h3>Dependency updates:</h3>

<ul>

<li>Update workflow pins and migrate Node matrices to modern versions by <a href="https://github.com/v-HarithaVattikuti"><code>@​v-HarithaVattikuti</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1583">actions/setup-node#1583</a></li>

<li>Upgrade <code>@​actions/cache</code> to 6.2.0 by <a href="https://github.com/philip-gai"><code>@​philip-gai</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1584">actions/setup-node#1584</a></li>

<li>Pin <code>@​types/node</code> to v24 by <a href="https://github.com/v-priyagupta108"><code>@​v-priyagupta108</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1585">actions/setup-node#1585</a></li>

<li>Override brace-expansion to 5.0.8 by <a href="https://github.com/v-priyagupta108"><code>@​v-priyagupta108</code></a> with <a href="https://github.com/Copilot"><code>@​Copilot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1599">actions/setup-node#1599</a></li>

<li>Upgrade actions/checkout from 7.0.0 to 7.0.1 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1598">actions/setup-node#1598</a></li>

<li>Upgrade prettier from 3.8.4 to 3.9.6 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1590">actions/setup-node#1590</a></li>

<li>Upgrade <code>@​vercel/ncc</code> from 0.44.0 to 0.45.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1610">actions/setup-node#1610</a></li>

<li>Upgrade pnpm/action-setup from 6.0.9 to 6.0.10 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1602">actions/setup-node#1602</a></li>

<li>Upgrade baseline-browser-mapping from 2.10.38 to 2.11.22 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1629">actions/setup-node#1629</a></li>

<li>Upgrade <code>@​types/semver</code> from 7.7.1 to 7.8.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1616">actions/setup-node#1616</a></li>

<li>Upgrade <code>@​typescript-eslint/parser</code> from 8.62.0 to 8.70.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1615">actions/setup-node#1615</a></li>

<li>Upgrade pnpm/action-setup from 6.0.10 to 6.1.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1631">actions/setup-node#1631</a></li>

<li>Upgrade jest-each from 30.4.1 to 30.5.2 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1636">actions/setup-node#1636</a></li>

<li>Upgrade eslint-plugin-n from 18.1.0 to 18.3.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1638">actions/setup-node#1638</a></li>

<li>Update dependencies and add license files by <a href="https://github.com/v-HarithaVattikuti"><code>@​v-HarithaVattikuti</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1642">actions/setup-node#1642</a></li>

<li>Upgrade eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1635">actions/setup-node#1635</a></li>

</ul>

<h2>New Contributors</h2>

<ul>

<li><a href="https://github.com/v-jitenderpalsingh"><code>@​v-jitenderpalsingh</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-node/pull/1580">actions/setup-node#1580</a></li>

<li><a href="https://github.com/philip-gai"><code>@​philip-gai</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-node/pull/1584">actions/setup-node#1584</a></li>

<li><a href="https://github.com/gperdomor"><code>@​gperdomor</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-node/pull/1421">actions/setup-node#1421</a></li>

<li><a href="https://github.com/SubJunk"><code>@​SubJunk</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-node/pull/1603">actions/setup-node#1603</a></li>

</ul>

<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-node/compare/v7.0.0...v7.1.0">https://github.com/actions/setup-node/compare/v7.0.0...v7.1.0</a></p>

</blockquote>

</details>

<details>

<summary>Commits</summary>

<ul>

<li><a href="https://github.com/actions/setup-node/commit/949feb2413d6458794dcd2491c4babbbce0c15c1"><code>949feb2</code></a> Bump eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 (<a href="https://redirect.github.com/actions/setup-node/issues/1635">#1635</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/7207c4f1189c7ee83ddf20c7c68bd1af6fdd751c"><code>7207c4f</code></a> chore: update dependencies and add license files (<a href="https://redirect.github.com/actions/setup-node/issues/1642">#1642</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/54337e0d02de9202d0948aaff36ad556375497b9"><code>54337e0</code></a> Bump eslint-plugin-n from 18.1.0 to 18.3.0 (<a href="https://redirect.github.com/actions/setup-node/issues/1638">#1638</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/fb54fa8c14c63410cc752f0ae3b7b3ca6af161fc"><code>fb54fa8</code></a> Bump jest-each from 30.4.1 to 30.5.2 (<a href="https://redirect.github.com/actions/setup-node/issues/1636">#1636</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/7f84f1d52d0c56afb45c62fee31a93b843cea4d6"><code>7f84f1d</code></a> Bump pnpm/action-setup from 6.0.10 to 6.1.0 (<a href="https://redirect.github.com/actions/setup-node/issues/1631">#1631</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/0c54c7b07420dcba69a7d832587f55ebdf771c9e"><code>0c54c7b</code></a> Bump <code>@​typescript-eslint/parser</code> from 8.62.0 to 8.70.0 (<a href="https://redirect.github.com/actions/setup-node/issues/1615">#1615</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/a8294190049a9c296f01b9a432aff41dd83d8284"><code>a829419</code></a> Bump <code>@​types/semver</code> from 7.7.1 to 7.8.0 (<a href="https://redirect.github.com/actions/setup-node/issues/1616">#1616</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/680d1e489b82f1243de15bc7665c0007e3c9a860"><code>680d1e4</code></a> Support absolute paths in node-version-file (<a href="https://redirect.github.com/actions/setup-node/issues/1633">#1633</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/db0fb3a98ed314b69026b6e8c9be26a7e2fe65a8"><code>db0fb3a</code></a> Bump baseline-browser-mapping from 2.10.38 to 2.11.22 (<a href="https://redirect.github.com/actions/setup-node/issues/1629">#1629</a>)</li>

<li><a href="https://github.com/actions/setup-node/commit/94196ee1d15439c1b6651cd87ef14e88ec435966"><code>94196ee</code></a> Bump pnpm/action-setup from 6.0.9 to 6.0.10 (<a href="https://redirect.github.com/actions/setup-node/issues/1602">#1602</a>)</li>

<li>Additional commits viewable in <a href="https://github.com/actions/setup-node/compare/820762786026740c76f36085b0efc47a31fe5020...949feb2413d6458794dcd2491c4babbbce0c15c1">compare view</a></li>

</ul>

</details>

<br />

#26 — 003-fix-openapi-viewer @mwrshah  no labels

- Validate JSON for both the skill and OpenAPI documents before rendering.

- Display the complete OpenAPI source without the false invalid-JSON warning or per-token rendering overhead.

- Preserve skill syntax highlighting and the original-text fallback for malformed JSON.

#25 — 002-legacy-api-aliases @mwrshah  no labels

- Restore legacy /api discovery, document, feedback and operator URLs as aliases for the existing root handlers, without redirects.

- Restore /api/v1/openapi.json and allowlisted /api/v1 source operations while preserving authorization, query strings, headers, request bodies and feedback deduplication.

- Keep root URLs canonical and extend deployment smoke checks for legacy URLs; no dependencies, storage changes or additional source capabilities.

- Validated locally with pnpm check, build, offline synthesis, dependency audit, Docker build and a synthetic alias/authentication/feedback smoke check. No live deployment performed.

#23 — 001-rhodes-access-governance @mwrshah  no labels

- Add WorkOS sign-in and scoped self-service Rhodes keys while preserving existing registry keys through one explicit authorization boundary.

- Remove operator privileges and triage routes; standardize feedback intake and root discovery/native routes while preserving all 45 published operations.

- Keep the existing Rhodes stack, hosting, retained stores and source credential; extend the existing release workflow with validation-secret and source checks.

- Prepare the dedicated production WorkOS application, personal-key permission and owned credentials. The Rhodes-only IAM update and release variables are applied and verified; existing GitHub OIDC trust is unchanged. Production deployment remains pending.

#2074 — 1417-invite-dss-membership @mwrshah  approved

- Clear accessRevokedAt when an authorized operator successfully re-provisions a revoked existing user.

- Queue the existing WorkOS sync in the same transaction so it targets active access.

- Report reactivated access explicitly; preserve role ceilings and DSS's separate inactive-membership admission policy.

#23 — 2035-name-validation-layout @mwrshah  no labels

- Keep the API key name, expiry control, and submit button aligned when inline validation appears.

- Preserve accessible error messages, focus handling, and mobile stacking with a CSS-only change.

- Verified both rendered implementations at six viewport widths with name, expiry, and combined errors using mocked API responses.

- Local Biome, TypeScript, Knip, and full Codedecorum checks pass.

#22 — 2034-builder-team-site @mwrshah  no labels

- Add the AI Builder Team homepage, short privacy policy, and terms of service.

- Include transparent logo, white-background favicon, and GCP branding PNG.

- Record the existing S3/CloudFront hosting configuration and publication process.

- Site is already live at https://builder-team.ai; this PR preserves its source without changing DSS runtime deployments.

#2073 — 1416-aerie-release-prep @mwrshah  no labels

## Narrow, low-risk change: only negative enrollment forecasts change

Read-only evaluation of the exact edited SQL expression against all 854 current warehouse level rows changes only the three negative results to zero. Every positive value, existing zero, and null stays unchanged. Underlying inputs and school-level forecast totals are untouched. This bounds the impact on the checked data; it does not replace PR validation.

## Changes

- Clamp final End-of-Year level enrollment to greatest(0, floor(...)) in the owning dbt model. Preserve unavailable nulls, raw operands, and school-level forecasts; no redistribution or validator changes.

- Align the existing formula assertion with the clamp. No new tests added.

- Evaluated the exact edited SQL expression read-only against all 854 current warehouse level rows: Fort Worth Middle School -1 → 0, Fort Worth Wonder Lab -1 → 0, Nova Academy Austin Middle School -2 → 0. No nonnegative values or nulls change.

- Follow-up for release #2072. Current level sums rise from 12 to 14 for Fort Worth and 11 to 13 for Nova Austin; school forecasts remain 12 and 11. This is the requested zero floor, not a reconciliation adjustment.

- No warehouse rebuild, Convex publication, production merge, or deployment performed. After merge to main, rebuild the affected warehouse models and run the forecast-only dev refresh before repeating exact-head release smoke.

#4 — 006-streamline-dss-recipe @mwrshah  no labels

- Require existing active DSS organization membership without automatic enrollment or upstream-org coupling.

- Separate provider setup from deployment; retain both secrets and narrow runner reads to validation only.

- Introduce support API 5 with explicit existing-hub migration guidance.

- Deduplicate OpenAPI responses and publish exact served-document size and token metadata.

- Convert component styling to Tailwind v4 utilities while preserving the existing palette.

- Update recipe documentation and existing API compatibility expectations.

#20 — 2033-2salesforce-renewals @mwrshah  no labels

- Preserve complete authorized read-only access while using business adoption to prioritize explanations and examples.

- Clarify OpenAPI deduplication, response fidelity, size metadata, and large native metadata discovery; retain the approved seek-and-expand instructions.

- Strengthen field provenance, currency semantics, and cross-document consistency guidance.

- Merge origin/main and preserve its DSS-only membership requirements.

#19 — 2032-salesforce-renewals @mwrshah  no labels

- Deduplicate OpenAPI, describe native response envelopes, and publish exact document sizes with business-oriented discovery guidance and the canonical contract pin.

- Clarify renewal currency measures, correct history examples, and remove stale observations and references.

- Require existing active DSS organization membership without automatic enrollment; retain single-service caller-key scope.

- Remove deployment-time WorkOS setup and readiness probes; retain both secrets and restrict direct deployment secret reads to validation only.

- Move component styling to Tailwind v4 utilities with the existing palette centralized in one theme stylesheet.

- Align hub authoring and release guidance; leave BrainLift approval, feedback operations, and external recipe migration pending.

#18 — 2031-key-copy-layout @mwrshah  no labels

- Keep copy confirmation and refresh loading inside fixed-size Lucide icon slots, with accessible feedback and no visible status insertion.

- Expand key management to the card width, compact the date columns, and use local YYYY-MM-DD HH:mm timestamps.

- Clarify read-only source access plus feedback submission, remove redundant UI copy, and add UI-scoped @/ imports support.

- Preserve the existing two-membership authorization policy.

#3 — 005-standardize-key-ui @mwrshah  no labels

- Align the canonical React key-management template with the Salesforce UI: full-width layout, compact date columns, and local YYYY-MM-DD HH:mm timestamps.

- Use packaged Lucide icons for stable copy confirmation and refresh loading, with accessible non-reflowing status feedback.

- Clarify read-only source access plus feedback submission, remove redundant headings and membership copy, and configure UI-scoped @/ imports.

- Preserve backend authorization and document the UI conventions.

#17 — 2030-2dss-prod-release @mwrshah  no labels

- Move WorkOS permission registration, personal-key enablement, and initial validation-key provisioning into one-time local DSS onboarding.

- Document the verified management API, preservation of existing enabled scopes, exact environment/user checks, and private credential handling.

- Update creation and release guidance while keeping provider approvals, authenticated release checks, and existing executable workflow migration separate.

Validation: Biome, TypeScript, Knip, Codedecorum, local documentation links, and whitespace checks passed.

#2070 — 1414-workos-sync-status-retry @mwrshah  approved

- Persist WorkOS DSS sync/removal status and safe failure messages; prevent stale jobs from overwriting newer attempts.

- Add confirmed Push to WorkOS / Retry WorkOS removal controls, with persistent red failure styling until verified success.

- Audit retry requests and preserve provenance-independent revocation and late-link cleanup.

- Leave Forge membership and capacity automation unchanged.

#15 — 2029-salesforce-key-ui @mwrshah  no labels

- Simplify personal-key creation with a Tailwind calendar, 30/90/360-day presets, and separate auth/list/error states; remove retry controls and component CSS.

- Surface actionable server errors through Sonner, preserve inline field validation and safe WorkOS support references, and distinguish confirmed rejection from genuine lost-response outcomes.

- Capture redacted structured WorkOS failures in the existing CloudWatch log stream without treating server credentials as expired user sessions.

- Register the service permission and verify scoped key issuance/revocation before runtime publication, with service-owned secret access.

- Update the creation skill with API 4 recipe guidance and explicit provider/deployment prerequisites.

#2071 — 1415-aerie-history-alignment @mwrshah  no labels

- Join current production history into main with a two-parent merge commit; no source changes, migrations, deployment, or production branch updates.

- Parents: main 56f702aaa4ffdc0385ebff4658b2c3c0dea3e6c4, production c4aa26fe46c55b038c295286a22720bc19a89433. Both are verified ancestors of head 0523dbca52fb45c43356ea57dbb3e4258863cc9f.

- The conflict-free merge and main share exact tree a81c6983808dd365a4627018ef36a18973aa0cd2; git diff origin/main HEAD is empty. The commit count reflects existing production history, not new source edits.

- Merge using Create a merge commit, never squash or rebase: those methods discard the production ancestry this PR preserves. The Main ruleset currently allows only squash; an administrator must permit merge commits while retaining required checks, approval, and thread resolution. Repository merge-commit support is already enabled.

- Before merging, reconfirm both branch tips are included and the source tree still equals current main. After merging, verify git merge-base --is-ancestor origin/production origin/main succeeds. Future production-only release commits can require another back-merge.

#2069 — 1413-implement-aerie-lifecycle @mwrshah  approved

- Create/link real Aerie users in WorkOS with deployment-scoped IDs, Clerk provenance, and shared DSS membership.

- Reuse verified, active DSS users created by support; fill missing Aerie breadcrumbs without replacing identities, roles, or unrelated metadata. Reject conflicting provenance and ambiguous matches.

- Add explicit Aerie revocation that deactivates DSS membership; preserve Clerk login, existing Aerie IDs/roles, and separate Forge tenancy.

- Configure enrollment through DSS_WORKOS_ORGANIZATION_ID; production DSS backfill completed for 192 people.

- Supersedes closed PR #2068. Temporary localhost UI preview removed.

- Remaining Aerie UI work: persisted sync-failure status and the real confirmation/retry button are not implemented.

- Separate DSS-Hub cutover: replace dual-org checks and enrollment writes with active DSS membership checks only.

#1 — 002-implement-dss-recipe-access @mwrshah  no labels

- Implement canonical two-org authorization with the fixed approved Aerie/shared-DSS organization pair and derived dss-<slug>:access permissions.

- Replace the key widget with server-mediated personal key management and a custom UI, including scoped listing/revocation, idempotent creation and one-time secret recovery.

- Enforce live memberships and exact key scope on protected requests; preserve public discovery, OAuth/session security and private feedback boundaries.

- Introduce support API 3, remove runtime org selectors, and document the explicit API-2 upgrade and service cutover contract.

- Update generation, dependency metadata, README and FEATURE documentation. Recipe revision: 1ad2c9a.

#3882 — feat(spacex-valuation): improve realized sales groups @sanketghia  approved

## Summary

- Group realized share sales by sale date, with each date collapsed by default and controls to expand or collapse the history.

- Show date-level totals, distinct fund count, and weighted cost per net LP share while retaining the existing allocation columns.

## Verification

- pnpm lint:pr

- Direct ESLint on RealizedSales.tsx

- Prettier check on RealizedSales.tsx

- pnpm tsc -p tsconfig.app.json --noEmit

- Tests were not run.

## Screenshots

<img width="2854" height="1188" alt="image" src="https://github.com/user-attachments/assets/b32fa77d-56f7-4a30-9ad7-039ad603f8b2" />

<img width="2886" height="1448" alt="image" src="https://github.com/user-attachments/assets/868fe293-e1fa-49b8-8b80-d9279f31bb1a" />

#2 — 003-align-session-status @mwrshah  no labels

- Align the template homepage's session-status handling with the current Salesforce implementation.

- Distinguish access denial (403), expired authentication (401), and unavailable session checks.

- Fetch session status without caching or following redirects; preserve service-neutral wording and existing sign-out controls.

#13 — 2028-implement-dss-skill-access @mwrshah  no labels

- Fix the approved Aerie/DSS org pair in service metadata instead of runtime environment selection.

- Remove org secret/ECS/CI field requirements and require inherited-variable stripping.

- Keep exact-pair startup verification and disposable test-only org injection.

#12 — 2027-implement-dss-hub-access @mwrshah  no labels

- Require live active Aerie and shared-DSS memberships, with absent-only DSS enrollment.

- Replace the key widget with backend-owned scoped key management and a custom portal; enforce exact Salesforce permission for listing, creation, revocation and API access.

- Hardcode the approved production Aerie/shared-DSS organization pair, remove runtime org selection, and document scoped-key cutover and secure rollback while preserving public discovery, Salesforce operations and independent releases.

- Keep production rollout, permission registration and key rotation separately approved; production lifecycle tracking remains gated on Aerie Gate A.

#11 — 2028-implement-dss-skill-access @mwrshah  no labels

- Require shared Aerie/DSS membership, absent-only enrollment and single-service personal keys in creation instructions.

- Define custom backend key management, live enforcement, strict legacy-key cutover and secure rollback.

- Separate recipe/support, lifecycle, provider, distribution and release gates while preserving canonical discovery guidance.

#10 — 010-bundle-dss-skill @mwrshah  no labels

- Bundle the complete create-dss-server skill, including references and scripts, under skills/.

- Link the bundled skill from the README; preserve the original localskills copy.

#8 — salesforce-dss-discovery-guidance @mwrshah  no labels

- Separate Salesforce runtime credentials and deployment-validation caller keys into service/environment-owned AWS Secrets Manager objects, with distinct validated ARNs and scoped direct IAM reads.

- Load TRILOGY_SALESFORCE_DSS_API_KEY through AWS OIDC before image publication; remove the GitHub secret alias, keep caller keys out of local runtime, and pass authenticated headers through stdin.

- Preserve current main's prod release gates, single OIDC deployment role, immutable-image release flow and resource identities. Keep the provisioned secret ARNs in infra/production.json.

- Apply the approved production cutover: new stores verified against existing values, deployment IAM/resources updated, and ECS rolled to the new runtime reference using the unchanged application image. Live health/public access, anonymous denial, authenticated Salesforce discovery and local loading passed; IAM simulation confirms separate direct secret reads.

- Retire ENV_DSS_HUB: it is inaccessible and scheduled for deletion on 2026-10-29 with a seven-day recovery window. Credential values, WorkOS identity and Salesforce integration remain unchanged. Document service-owned boundaries, independent deployment/rollback and migration operations.

#3881 — fix(performance-review): omit full filters from URL @sanketghia  approved

## Summary

- Omit BU and class query parameters when the complete available set is selected, relying on page defaults after reload.

- Preserve URL values for explicit subsets.

- Prevents the default all-selected Performance Review URL from exceeding CloudFront's 8,192-byte limit.

## Test plan

- pnpm lint:pr

- pnpm exec prettier --check src/shells/DesktopShell/useFilterUrlSync.ts src/shells/DesktopShell/FiltersContext.tsx

- pnpm tsc -p tsconfig.app.json --noEmit

- Automated tests not run.

#3879 — fix(spacex): reorder Q3 availability timeline @sanketghia  approved

## Summary

- Reorder the combined availability timeline so Q3 2026 earnings release (22-Oct-26) precedes Day 135 (26-Oct-26).

- Align the default ladders, schedule rows, and snapshot/calculation fixtures with the synced workbook order.

## Test plan

- Passed: targeted ESLint, Prettier, TypeScript check, full frontend Vitest suite (6,950 passed, 16 skipped), and production build.

- Passed: Ruff 0.15.22 format check and lint; Ruff reported an existing invalid # noqa directive at services/docx_reports/memo_data/group_defaults.py:33.

- Backend pytest did not collect cleanly: four unrelated collection errors in test_joe_charts_formula_parity.py, test_comment_service_cache.py, test_migrate_unblended_budget_v2.py, and test_redshift_handler_pool.py. No backend files changed.

## Screenshot

<img width="1372" height="843" alt="image" src="https://github.com/user-attachments/assets/ca6e3c42-f8b1-4c58-bcf7-f59cce58499f" />

#2063 — Remove End-of-Year comparison research doc @vvp-trilogy  approved

## Summary

- remove the End-of-Year by-level comparison research document

- remove its documentation index entry

## Validation

- git diff --check

- verified no remaining references to the removed document

#2064 — Admissions: publish and display End-of-Year forecast by level @vvp-trilogy  approved

## Summary

- extend the Forecast V2 by-level publication with production End-of-Year status, operands, and final forecasts

- expose a bounded seven-level End-of-Year breakdown through the existing authenticated public Forecast API

- add the sixth End-of-Year by-level card and Share columns for both January and End-of-Year tables

- preserve rollout compatibility and fail closed on incomplete or malformed level publications

## Validation

- pnpm --dir packages/contracts exec vitest run src/admissions-forecast-v2.test.ts --maxWorkers=1

- pnpm --dir sync exec vitest run src/redshift/admissions-forecast.test.ts --maxWorkers=1

- pnpm --dir chat exec vitest run convex/publicApi/v2/admissions.test.ts --maxWorkers=1

- pnpm --dir chat exec vitest run components/dashboards/admissions/forecast/v2/__tests__/forecast-v2-report.test.tsx --maxWorkers=1

- pnpm typecheck (all affected package checks passed; final aggregate run was split into the two Chat tsc commands after a long silent aggregate process)

- pnpm --dir chat exec tsc --noEmit

- pnpm --dir chat exec tsc -p convex/tsconfig.json --noEmit

- pnpm lint:test-architecture

- pnpm lint:read-bounds

- pnpm biome check on all changed files

Closes #2062

#2190 — Daily QuickBooks unmapped Class digest — internal only @ashwanth1109  no labels

## Business Value

Provide a daily view of unresolved QuickBooks Class-to-School assignments by file, covering the current school year since 1 July. The email includes a full grouped CSV with signed expense/revenue and posting counts, with classless postings shown separately. Unresolved assignments may be intentional.

## Implementation

- Add an independent reporting Lambda over accepted Core postings, validating publication/ledger counts, freshness, immutable source provenance, School assignment compatibility and independent accounting totals.

- Live daily at 10:00 UTC, addressed only to ashwanth.r@trilogy.com for now. Both recipient audiences and SES IAM enforce that single address. The production-only deployment allowlist excludes the digest from dev stacks and registry publication; runtime rejects non-prod before AWS access.

- Fence final School compatibility with mapping-generation reads. If the generation changes, recheck compatibility once; incompatible assignments, changing Core inputs or continuous generation movement fail before delivery.

- Audit every non-system relation before adding reader grants, rejecting excess table/column privileges and unreviewed memberships. Require all three explicit accounting partitions and their measures, and neutralize formula-like CSV source text while preserving raw evidence and signed amounts.

- Save immutable report/MIME evidence. Fetch and checksum-verify the frozen MIME before acquiring a daily delivery claim so preparation failures can retry. Same-day retries skip verified receipts; ambiguous SES attempts remain blocked for reconciliation.

- Keep whole-table readiness because the Core writer atomically replaces the entire fact. Historical ledger entries are supported; mixed fact generations indicate contamination and are rejected.

## Validation

- Latest main (55fa4e51) is incorporated into head 97317afe. 151 Python tests, 1,013 CDK tests, TypeScript compilation and scoped Ruff checks pass. The full CDK suite ran in a clean snapshot of this head.

- Added 23 tests executing the shipped readiness SQL, precise inter-query mapping-race tests, retry tests for pre-claim S3 timeout/checksum failure, and reader-audit regression coverage. An actual-entrypoint dev synthesis test checks both stack and registry exclusion; the daily rule test requires production mode in its target input.

- Live audit-only verification inspected 3,559 relations and confirmed exactly the seven approved SELECTs, with no unreviewed roles/groups or column grants; no grants were changed. The live owning procedure confirms whole-table replacement and a retained publication ledger.

- Deployed only Pipeline-quickbooks-unmapped-class-report-prod with --exclusively; verified [1/1], CloudFormation completion and exact deployed Python/SQL. Only the Lambda code changed in this stack.

- Supported live workflows on 21 October: preview validate-qb-review-preview-20261021T041652Z validated all 39 groups and matched the independent preflight CSV; validate-qb-review-self-test-20261021T041912Z sent one test email only to ashwanth.r@trilogy.com; validate-qb-review-duplicate-check-20261021T041937Z skipped the duplicate using the same verified receipt. All three run records are SUCCESS with failure notifications suppressed. Today's production claim was untouched, and the enabled daily rule still targets production mode at 10:00 UTC.

- Review responses include the detailed evidence, starting at https://github.com/AI-Builder-Team/Surtr/pull/2190#discussion_r4333003580. Historical execution evidence remains in pipelines/runners/quickbooks-unmapped-class-report/VALIDATION.md.

## Implementation Effort

Approximately 3–4 engineering days for an average engineer to implement the accounting/readiness contract, runner/access controls, safe delivery state, deployment isolation, regression coverage and live validation without AI assistance.

## Linear

https://linear.app/builder-team/issue/SURTR-1650

#2060 — Admissions: forecast End-of-Year enrollment by level @vvp-trilogy  approved

## Summary

- calculate End-of-Year roster, additions, and headlines independently for all seven canonical student levels

- add level-grain historical and weekly-pace candidates plus complete-snapshot history and atomic lock resolution

- publish additive End-of-Year fields without changing the January contract or model version

- document the PR-warehouse comparison against the canonical program totals

## Validation

- dbt compile for all affected models

- isolated pr2059_ warehouse build through mart_admissions_forecast_by_level

- 37 focused schema/data tests passed, including formula, seven-level coverage, atomic conservation, and history completeness

- comparison: 61/61 roster and atomic-operand reconciliations; 40/61 exact final headlines; remaining deltas (-4 to +1) explained by independent rounding in docs/admission/end-of-year-forecast-by-level-comparison.md

Closes #2059

#2058 — Expose Forecast usage mode and simplify Pipeline controls @vvp-trilogy  approved

## Summary

- add shared Program/Physical controls to the Forecast V2 toolbar on desktop and mobile

- reuse the same focused usage-mode popover in Pipeline and remove its sort builder

- make Pipeline header sorting single-column even when Shift is held

- keep Forecast CSV export at the right edge of the report action group

## Validation

- pnpm --dir chat exec vitest run components/dashboards/admissions/forecast/v2/__tests__/forecast-v2-report.test.tsx --maxWorkers=1

- pnpm --dir chat exec vitest run components/dashboards/admissions/forecast/v2/__tests__/forecast-v2-view.test.tsx --maxWorkers=1

- pnpm --dir chat exec vitest run components/dashboards/admissions/pipeline/derivation.node.test.ts --maxWorkers=1

- pnpm --dir chat exec vitest run components/dashboards/admissions/pipeline/pipeline-matrix.test.tsx components/dashboards/admissions/shared/__tests__/usage-mode.test.tsx --maxWorkers=1

- pnpm typecheck

- pnpm lint:test-architecture

- Biome check for all changed files

Closes #2057

#3877 — fix(acquisition-performance): assign Contently to Kathy @sanketghia  approved

## Summary

- Assign Contently to Kathy in the acquisition performance review and Joe Charts summary.

- Update the current source inventory and lineage diagram.

## Verification

- Backend: Ruff passed; 95 focused tests passed; Pyright reported 0 errors and 1 existing warning at an unchanged line.

- Frontend: lint, Prettier, TypeScript, and Vitest passed (6,950 passed, 16 skipped).

## Screenshot

<img width="816" height="775" alt="image" src="https://github.com/user-attachments/assets/a1dd9cfd-fca5-4f41-a0c7-fa4f684c1a17" />

#2168 — Publish approved Crossover school mappings and staffing affiliations @ashwanth1109  approvedmercy-allow-critical

## Business Value

Publish Finance-approved Crossover affiliations into the existing canonical School identity map and use them for Guide staffing eligibility. Stable team IDs keep room renames from changing ownership, and explicitly approved non-campus destinations remain separate from Schools. QuickBooks posting spend is preserved.

## Changes

- Publish a ledger-reconciled, atomic observed-room directory from native XO team IDs, retaining IDs across renames and exposing first/last invoice weeks. A real XO pipeline-success event refreshes this directory independently of the existing sources.

- Export Aerie approval metadata and scoped/non-campus rules through Rhodes. Require all six coherent raw publications in Core, extend the existing xref_school_source with crossover/teamroom, and atomically publish the governed affiliation reference alongside the ontology.

- Extend dim_school_identity with current native room IDs/names and a version 2 identity hash; add explicit mapping coverage. Include an atomic restricted view-recreation migration because Redshift cannot replace an existing view with extra columns.

- Replace Guide room-name inference with approved current affiliations. Native contractor IDs resolve first; name fallback must be unique. Exact person > exact title > room precedence avoids duplicate counts. Known unmapped/ambiguous Guide evidence fails before target replacement, retaining last-good output and all original QuickBooks spend.

- Preserve the legacy QTD affiliation table and existing Finalsite/source contracts. Document the staged rollout, precise isolated stack targets, prerequisite gates and rollback behavior in CROSSOVER_ROLLOUT.md.

Companion Aerie PR: https://github.com/AI-Builder-Team/Aerie/pull/1909

## Reviewed data scope

Column F's explicit changes are accepted as reviewed destinations under the user's instruction. The prepared Aerie plan contains 256 ready decisions (219 campus and 37 non-campus). TSA Onsite remains pending, as do two clarification rows and four potentially legacy rooms; the pending title-rule tab is not imported. Seven newly observed IDs absent from the workbook stay unmapped.

## Validation

- 928 focused Python tests pass: Core ontology 91; Rhodes staging 207; source directory 76; the full financial pipeline suite 554. Tests cover native IDs across renames, duplicate-name safety, exact rule precedence, exclusive periods, preserved spend, approval projection, source/event gates and shared lock ordering.

- Two focused CDK tests pass, verifying the real directory manifest has all four triggers and preserves the XO upstream execution context and notification suppression.

- Read-only live execution of the candidate directory SELECT returned 270 rooms and all 256 ready workbook IDs. Latest accepted XO publication: 2026-10-15 07:30:23 UTC; 1,662 fetched/published invoice rows.

- The candidate identity SELECT runs against live inputs with its directory supplied as a read-only CTE: 118 Schools and the existing 58 Finalsite-linked Schools. No candidate mappings were imported by this check.

- Changed Python files are formatted. Ruff baseline comparison finds no newly introduced diagnostics (28 existing findings in changed files versus 33 at base). No unrelated files were linted or formatted. git diff --check passes.

## Review follow-up — 20 October 2026

- Merged current main, retaining both Crossover and Finance lock-order coverage and all Rhodes API coverage tests.

- Guide/Lead Guide publication now requires an approved School, other-School or non-campus affiliation. Missing XO identities, unmapped/ambiguous evidence and unknown/null statuses fail before target replacement; original posting spend remains unchanged.

- The Core verifier validates the source run ID against the runner's shared 1–128 character allowlist before connecting or building any query.

- The Rhodes SchoolLink rejection finding was not reproducible: the reviewed transform already accepts xoTeamroom. Added active/archived link projection assertions and native team-ID regression cases.

- Current local validation: 1,225 Python tests pass across Core (100), Rhodes (298), source directories (76) and financials (751); two live financial integration tests are skipped. All 34 pipeline construct CDK tests pass. Ruff 0.15.22 lint/format pass for the five Python files changed in this follow-up; git diff --check origin/main passes.

- No production deployment or pipeline invocation occurred. The staged pre-merge live-validation requirements below still apply.

## BLOCKERS / pre-merge live validation

Pre-merge live validation remains blocked. No production schema/stack deployment, mapping import or candidate pipeline execution has occurred. User authorization is still needed for the staged candidate deployments against shared production schemas. The user has confirmed Marcin Pindral as reviewer and 15 October 2026 00:00 IST as the current-only effective cutover; the import plan now records that confirmation. No historical ownership before the cutover is asserted.

Before merge, deploy each affected candidate stack independently with --exclusively, verify CloudFormation events, trigger the required producer/affected pipeline with inherited failure-notification suppression, monitor terminal execution and reconcile the outputs. Deployment alone and read-only SELECT checks do not satisfy live validation. Preflight unresolved Guide evidence before running that consumer; report a data blocker rather than invoking a guaranteed failure or weakening the gate.

## Implementation Effort

Estimated 4–6 engineer-days for an average engineer to hand-code and test the four pipeline contracts, governed publication, SQL consumer changes, migrations and rollout workflow without AI assistance, excluding production validation and Finance wait time.

## Linear

https://linear.app/builder-team/issue/SURTR-1469/encode-finance-teamroom-rulings-in-ref-qtd-hc-teamroom-affiliation-r1

https://linear.app/builder-team/issue/SURTR-1478/tsa-onsite-platformcorporate-title-rule-in-ref-qtd-hc-title-role-r2

#2184 — fix(alpha): persist verified daily publication settings @marcusdAIy  no labels

## Summary

- Persist the already-live Alpha daily settings in source: 10:00 UTC schedule enabled, PUBLICATION_MODE=automatic, one-time publication controls empty.

- Align the release verifier’s terminal Lambda and schedule expectations, focused regression tests, and the operator README with the achieved production state.

## Production evidence (October 19, 2026)

- First new-host snapshot committed: run alpha-cutover-b88ee31a06a5494faa4b3c7377b355db, 72 schools and 433 endpoints; warehouse published ledger matches the result.

- Read-only data/deployment verification completed with warehouse privilege checks explicitly skipped at Marcus’s request, and local compatibility adjustments for large Redshift SUPER payloads, nullable/UTC source timestamps, and report serialization. The unmodified release verifier did not pass; this PR does not claim it did.

- Live Lambda is automatic with empty controlled fields and the exact reviewed code SHA; the daily rule is enabled at cron(0 10 ? * * *). The next scheduled publication has not run.

## Checks

- uv run pytest -q (Alpha runner)

- uv run ruff check scripts/verify_release.py tests/test_verify_release.py

- uv run pyright scripts/verify_release.py

- npm test -- --runInBand test/real-pipeline-configs.test.ts (621 passed)

- npm run build

- git diff --check

This PR does not deploy anything itself. Deployment after merge must confirm that production remains in automatic mode with the schedule enabled; it should not replay the historical controlled publication.

#2047 — fix(admin): show access denied on /admin/users instead of a fatal error (AERIE-2939) @marcusdAIy  approved

## Summary

AERIE-2939

Closes #2024

Visiting /admin/users without admin.users.read now shows an access-denied message instead of "An unexpected admin error occurred", and no longer creates a Platform Error.

## Why it's needed

Platform error group perr_v2_0i295mu1avrzjs. The users page subscribed to users.admin.listUsersWithRoles for every authenticated session. For anyone without admin.users.read, the server guard throws a plain Error, Convex masks it as Server Error, and the admin error boundary reports it as an unexpected render failure. Any non-admin who reaches the URL (bookmark, history, direct link) hits this every time.

## Changes

- chat/app/(main)/admin/users/page.tsx:

- listUsersWithRoles is skipped until the viewer's capabilities include admin.users.read.

- The page checks the same expanded capability set the server uses, via expandAerieCapabilityDependencies, so admin.users.manage and admin.users.provision still imply read.

- Once currentUser resolves without read access, the page renders "You do not have permission to view users." in the same style as the VIP page's denial.

- Admins see no change.

## Breaking changes

None.

## Test plan

- [x] New test in user-management.test.tsx: a viewer with only operations.portfolio.read sees the access-denied message, and listUsersWithRoles is never called.

- [x] Negative check: with the page change stashed, the new test fails.

- [x] vitest run app/(main)/admin/users: 26 passed. This includes the existing manage-only and provision-only cases.

- [x] tsc --noEmit (chat) and biome are clean.

#2048 — fix(tasks): show Team Tasks refresh state instead of crashing (AERIE-2936) @marcusdAIy  approved

## Summary

AERIE-2936

Closes #2020

While task projections rebuild, Team Tasks now shows "Team Tasks data is being updated. Try again shortly" with a retry button. Before, it showed a full-page error and filed a Platform Error.

## Why it's needed

Platform error groups perr_v2_0lzoa1u0jn5l4s and perr_v2_1vmnm331pimi3t. After a Site, Work Unit or Work Unit Group rename, listTeamCatalog and listTeamSearchChunks deliberately throw a typed ConvexError while projectionMaintenance reprojects the affected Tasks. docs/task-board/FEATURE.md describes this as a "clear data-is-being-updated message". The Team Tasks view didn't handle it, so the error reached AerieErrorBoundary. That replaced the whole workspace with "Team Tasks could not be loaded" and reported an unexpected render failure.

## Changes

- chat/components/task-board/team-tasks-view.tsx adds TeamTasksExpectedErrorBoundary inside the existing AerieErrorBoundary:

- A typed ConvexError renders its message in the shared TaskListState error state, with a retry that remounts the content. This mirrors My Tasks' list boundary.

- Any other error is rethrown during render, so AerieErrorBoundary still captures genuine failures as Platform Errors.

## Breaking changes

None.

## Test plan

- [x] New tests in team-tasks-view.test.tsx:

- When listTeamCatalog throws the "being updated" ConvexError, the message and retry appear. Clicking retry once the projection is ready renders the Task list.

- A plain Error still propagates to the outer boundary.

- [x] Negative check: with the view change stashed, the refresh test fails.

- [x] vitest run components/task-board: 121 passed.

- [x] tsc --noEmit (chat) and biome are clean.

#2045 — fix(documents): relink legacy generic documents that have no topic (AERIE-2938) @marcusdAIy  approved

## Summary

AERIE-2938

Closes #2022

Relinking the Drive file behind a legacy generic document that has no topic now succeeds instead of returning HTTP 500.

## Why it's needed

Platform error group perr_v2_1u1blwb1tdwxu5 recorded 45 occurrences in about 20 minutes, all from one admin retrying POST /v2/portfolio/sites/{siteRef}/documents/{documentRef}/relink on the same two documents.

The relink only sends Drive identity fields. But updateDocument re-ran normalizeDocumentTopic on every call, using the stored docType and topic. Generic documents (investigation, proposal, policyAndProcedure, other) filed before topics were required have no topic, so that check threw "Document topic is required for generic document types", which surfaced as an uncaught 500. Because the failure doesn't depend on anything the caller sends, retrying could never succeed.

## Changes

- updateDocument in chat/convex/rhodes/runtime/writes/documentWrites.ts skips topic validation when all of these hold:

- the request leaves docType and topic unchanged;

- the stored document is a generic type;

- it has no topic.

- This matches the legacyMissingGenericTopic handling that registerDocument, pendingLifecycle.ts and the v2 upload flow already use.

- Requests that set docType or topic are still validated, so you can't create a new topic-less generic document or blank out a topic.

- Not changed: v2 PATCH on documents. It already rejects a missing topic with a typed 422 rather than a 500.

## Breaking changes

None.

## Test plan

- [x] New test in rhodesMcpMutationParity.test.ts:

- Updating a legacy other document with no topic using relink-shaped args (Drive file ID and URL, externalUrl: null, MIME type) succeeds. The topic stays unset.

- Setting docType: "proposal" or a blank topic on that document still throws the required-topic error.

- [x] Negative check: with the source change stashed, the new test fails with "Document topic is required for generic document types".

- [x] vitest run convex/rhodesMcpMutationParity.test.ts convex/publicApi convex/rhodes convex/removeDueDiligenceReportLinkMigration.test.ts: 1056 passed.

- [x] tsc --noEmit (chat) and biome are clean.

#2046 — fix(api): return invalid_cursor for undecodable site-note list cursors (AERIE-2941) @marcusdAIy  approved

## Summary

AERIE-2941

Closes #2025

GET /v2/portfolio/sites/{siteRef}/notes now returns the existing 400 invalid_cursor when the inner Convex cursor can't be decoded, instead of HTTP 500.

## Why it's needed

Platform error group perr_v2_068ikob0g12mp5 recorded a single occurrence, but the defect is structural. The list handler checks the outer site-note cursor envelope, then passes sourceCursor straight to siteNotes.listNotes. If that inner cursor is stale or hand-built, Convex throws its native "Failed to parse cursor" error, which escapes the request boundary as internal_error. Every other paginated v2 domain (work management, portfolio, property, documents, backup sites) already catches this case with isInvalidConvexPaginationCursor.

## Changes

- listHandler in chat/convex/publicApi/v2/domains/siteNotes.ts wraps the listNotes call. When isInvalidConvexPaginationCursor matches, it throws the same 400 invalid_cursor the envelope check already uses. All other errors still propagate.

## Breaking changes

None.

## Test plan

- [x] New test in siteNotes.test.ts: a valid outer cursor wrapping a garbage sourceCursor returns 400 with code: "invalid_cursor".

- [x] Negative check: with the source change stashed, the same request returns 500 and logs [public-api-v2] unhandled error.

- [x] vitest run convex/publicApi/v2/siteNotes.test.ts convex/publicApi/v2/portfolioDomain.test.ts convex/publicApi/paginationErrors: 44 passed.

- [x] tsc --noEmit (chat) and biome are clean.

#2043 — fix(portfolio): wait for Convex auth before querying site sheet data (AERIE-2942) @marcusdAIy  approved

## Summary

AERIE-2942

Closes #2027

The Portfolio Site Detail page and its side panel now wait for Convex auth before subscribing to portfolio.siteSheetData.getForSite.

## Why it's needed

Platform error group perr_v2_0ac3rm01lat1xe shows 81 events from 8 users over about 10 weeks. Each one is a masked Server Error on Q(portfolio/siteSheetData:getForSite), and the user sees the Personnel and Schools Data Sheet cards fail to render.

The site row comes from usePortfolioSite, which loads it with a Next fetch authenticated by the Clerk cookie. So the layout can render, and fire the query, before the Convex client has its auth token. The query then hits requireCapability("operations.portfolio.read"), which throws a plain Error, and Convex masks the message.

## Changes

- New useSiteSheetData(site) hook. It passes "skip" until useConvexAuth().isAuthenticated is true. This is the guard pattern used by capex-view.tsx, funnel-view.tsx and others.

- site-detail-page.tsx and portfolio-detail-side-panel.tsx both use the hook instead of an unguarded useQuery.

- The cards' loading state is unchanged: undefined still means loading and null still means no sheet match. The cards just show loading a moment longer while auth settles.

- The existing site-detail test mock now includes useConvexAuth.

## Breaking changes

None.

## Test plan

- [x] New use-site-sheet-data.test.tsx:

- The query is skipped while auth is loading or unauthenticated.

- Once authenticated, it subscribes with the site lookup args.

- [x] Negative check: with the guard removed, both skip tests fail.

- [x] vitest run components/dashboards/portfolio: 735 passed.

- [x] tsc --noEmit (chat) and biome are clean.

- [ ] After deploy, watch perr_v2_0ac3rm01lat1xe for no new occurrences.

#2042 — fix(admissions): fail refresh runs orphaned by a worker restart (AERIE-2344) @marcusdAIy  approved

## Summary

AERIE-2344

When a new admissions refresh run starts, any older run still marked running is now marked failed with an "abandoned" reason, along with its unfinished domains.

## Why it's needed

When the analytics worker is recreated mid-run (for example during the release #1448 deploy on 2026-09-23), the in-flight admissionsRefreshRuns row stays running with no completedAt forever. Nothing reaped it, so every deploy or restart could leave one behind, and run history kept reporting it in flight.

## Changes

- startRefreshRun reaps abandoned runs in the same transaction. A run is abandoned if it is still running and started before the new run. Up to 25 are reaped per start.

- The run and its running domain rows become failed, with completedAt set and an errorSummary that names the run that superseded it.

- Completed domains and publication pointers are left untouched. The orphaned run's already-published forecast stays published.

- This is safe because the root analytics refresh reschedules itself with setTimeout after each run finishes, and prod runs a single analytics-worker. So a still-running older run can only mean its worker died. If a reaped run somehow finishes anyway, completeRefreshRun overwrites the status.

- No status reader gates on running (publication ordering uses startedAt), so this changes run history only, not what gets published.

- Not included: the optional SIGTERM hook and resuming or publishing completed domains after a restart. Reaping when the next run starts covers the orphaned rows, since a restarted worker runs a refresh immediately.

## Breaking changes

None.

## Test plan

- [x] vitest run convex/admissions/refreshRuns.test.ts: three new tests.

- An orphaned run and its running domain are failed with an abandoned reason that names the new run. Its completed and published forecast domain stays completed.

- Completed runs and runs started after the new one are left alone.

- Restarting the same run ID doesn't abandon itself.

- [x] Negative check: with the source change stashed, the orphaned-run test fails.

- [x] vitest run convex/admissions: 587 passed.

- [x] tsc --noEmit (chat) and biome are clean.

#2039 — fix(ui): Approved Capex grid column, sorted FTO CSV export, usage-mode aria-pressed (AERIE-2349) @marcusdAIy  approved

## Summary

Fixes three of the four UI defects from the release smoke test: All Sites now has an Approved Capex column, the FTO CSV export follows the on-screen sort, and the Program/Physical toggle exposes its pressed state. The fourth ("1 students") is already fixed on main.

AERIE-2349

## Why it's needed

- approvedCapex lives in PORTFOLIO_SITE_DETAIL_FIELD_DEFINITIONS (detail-card fields kept out of the grid and the API/MCP edit inventory). The grid builds its columns only from the main catalog, so the approvedCapex render case in grid-cell.tsx never ran.

- The FTO matrix sorts at render time, but handleExportCsv wrote the unsorted filteredSites.

- The usage-mode toggle buttons had no aria-pressed, so screen readers couldn't tell which mode was active.

## Changes

- chat/lib/all-sites-grid/columns.ts: adds approvedCapex to the grid as a read-only summary column. It sits after the last Opening column so it falls inside the Opening header band. The field stays out of the main catalog, so it is still not in the API/MCP edit inventory, and the Approved Capex card still owns edits. It is hidden by default, available in the column picker, and appears for users with a saved column layout, because the grid persists hidden columns rather than visible ones.

- chat/components/dashboards/fto/fto-pipeline-view.tsx: the CSV export applies applySorts(filteredSites, sortConfig, getSortValue) with the matrix's own sort-value function, which is now exported from fto-matrix.tsx.

- chat/components/dashboards/admissions/shared/usage-mode.tsx: adds aria-pressed to both buttons and wraps them in role="group" labeled "Usage mode". This is the shared toggle used by Forecast V2, Pipeline, Enrollments, and Demographics.

- Not changed: "1 students". StudentPanel already pluralizes, and Demographics passes "Unique Student" and "Unique Students".

## Breaking changes

None.

## Test plan

- [x] columns.node.test.ts: the Approved Capex column exists, follows an Opening column, and catalog columns keep their order.

- [x] fto-pipeline-view-persistence.test.tsx: with a persisted name-descending sort, the exported rows are Gamma, Beta, Alpha.

- [x] New usage-mode.test.tsx: aria-pressed follows the value, and the group has an accessible name.

- [x] Negative check: with the source changes stashed, all new tests fail.

- [x] pnpm vitest run for the admissions shared, FTO, all-sites-grid, and school-fields tests (548 passed).

- [x] tsc --noEmit and biome.

## Screenshots

From local Aerie (next dev against a personal dev Convex deployment) on this branch.

All Sites grid: column picker. Approved Capex is listed under Opening.

<img width="865" height="916" alt="image" src="https://github.com/user-attachments/assets/a53f5d23-8dac-48b8-be23-b3c03529d75b" />

All Sites grid: column on. Approved Capex sits under the Opening band. No dev site has approvals, so every cell shows the empty dash.

<img width="865" height="916" alt="image" src="https://github.com/user-attachments/assets/a2e10ac6-1aa4-4342-abd9-f7cc6429b15b" />

Buildout: sorted by Site, descending. I captured the CSV export's output in the page. It has the same 116 rows in the on-screen order, starting with PR-693, Dorado, PR 00692, Alpha Winter Park, Alpha New York City 787 11th Ave, and Alpha Miami.

<img width="865" height="916" alt="image" src="https://github.com/user-attachments/assets/2e2ade9e-f8d2-403f-a2ed-c31d1354d36a" />

Demographics: usage-mode toggle, Program then Physical. In the browser accessibility tree, Program reads pressed and Physical released; after clicking Physical they swap.

<img width="865" height="916" alt="image" src="https://github.com/user-attachments/assets/950bffd7-5d38-475d-be1d-59933075d35b" />

<img width="865" height="916" alt="image" src="https://github.com/user-attachments/assets/05ae4335-9889-4228-83b0-d2cf7ba00cf3" />

#2034 — fix(api): add write-gated siteNoteChange dictionary object for note write workflows (AERIE-2540) @marcusdAIy  approved

## Summary

Adds a write-gated collaboration.siteNoteChange dictionary object that lists the note write operations and operations.driSites.write, and points the three note-write workflows at it. collaboration.siteNote stays read-only, so keys with only portfolio-read access still see it.

AERIE-2540

## Why it's needed

The 9/25 hotfix narrowed collaboration.siteNote to its read operations so keys with only portfolio-read access could see it. The catalog validator requires an object to hold the capabilities of every operation it lists, and objects are hidden from callers missing any of those capabilities. The hotfix's three new write workflows (record-site-decision, correct-site-note, remove-site-note) still pointed at siteNote. So a reader following a workflow's semanticRef landed on an object listing neither the operation nor the capability the workflow calls. The ticket's acceptance criterion: every operationId and capability of a workflow appears on the dictionary object it references.

## Changes

- chat/lib/public-api/v2/domains/site-notes.ts:

- New collaboration.siteNoteChange object. It lists the list, create, update, and delete operations, requires portfolio read plus operations.driSites.write, has a writes relationship to collaboration.siteNote, and has a revision field that documents If-Match and the 412 behavior.

- The three write workflows now set semanticRefs to collaboration.siteNoteChange.

- collaboration.siteNote is unchanged.

## Breaking changes

None to the API. Agent-context documents change: writer keys see one more dictionary object, and three workflows have a different semanticRef. Read-only keys see the same dictionary as before.

## Test plan

- [x] New projection.node.test.ts case:

- A read-only key sees siteNote and not siteNoteChange.

- For a writer key, every note workflow's operationIds and capabilities are listed on the objects it references, which is the ticket's acceptance check.

- [x] Negative check: with site-notes.ts stashed, the new case fails

- [x] pnpm vitest run lib/public-api convex/publicApi passes, apart from skill-package.node.test.ts. That test also fails locally on clean main (a Windows-only hash mismatch) and passes in CI.

- [x] packages/contracts pnpm vitest run

- [x] tsc --noEmit and biome

#2033 — 1410-education-approval-name @mwrshah  approved

- Preserve education regulatory approval names when parsing Portfolio site data so the card heading and edit input show the stored name.

- Normalize approvals through the shared contract and cover named and unnamed records with regression tests.

- Confirmed the reported permit name exists in production Convex; no data migration or production mutation required.

#2032 — docs(api): mark due-diligence enablement as point-in-time and route status questions to review-site-status (AERIE-2534) @marcusdAIy  approved

## Summary

The inspectDueDiligenceFacts enablement workflow now carries the same point-in-time rule as the dictionary. Status questions are routed between it and portfolio.review-site-status in both directions.

AERIE-2534

## Why it's needed

The 9/25 hotfix added the point-in-time rule (as of dueDiligence.dateCompleted; the live record wins) only to the dictionary. A cold reader who starts from the enablement and asks a site-status question was still offered getPropertyDueDiligence as "approved property diligence state", with no caveat. Park City and Tulsa both have Complete cards whose zoning, regulatory, and open-date fields differ from their live records.

## Changes

- chat/lib/public-api/v2/domains/property.ts, inspectDueDiligenceFacts:

- The useWhen line now scopes the workflow to what diligence recorded as of completion.

- A new interpretation line mirrors the dictionary's point-in-time and live-record-wins rule.

- A new routeAway sends current-state questions (zoning, regulatory, open date, overall status) to portfolio.review-site-status.

- chat/lib/public-api/v2/domains/portfolio.ts, portfolio.review-site-status: a new routeAway says not to read the due-diligence card for current state.

## Breaking changes

None. This changes enablement text only; no operation or schema changes.

## Test plan

- [x] pnpm vitest run lib/public-api/v2/domains/property.node.test.ts lib/public-api/v2/domains/portfolio.node.test.ts (new assertions on both workflows)

- [x] Negative check: with the source changes stashed, both new assertions fail

- [x] pnpm vitest run lib/public-api lib/agent-context convex/publicApi

- skill-package.node.test.ts fails locally on clean main too (a Windows hash mismatch), so it is unrelated to this change.

- One v2/admissions test is a known flake; it passed on rerun.

- [x] tsc --noEmit and biome

#2031 — fix(sync): keep analytics worker up on invalid DBT_TARGET, preflight PR relations, log once (AERIE-2345) @marcusdAIy  approved

## Summary

An invalid DBT_TARGET no longer crash-loops the analytics worker. Only the dbt-backed refreshes fail, with a loud startup error. PR targets get a startup preflight that warns when their relations are missing, and the [dbt] relation log now prints once per target and relation instead of on every refresh.

AERIE-2345

## Why it's needed

The worker parsed DBT_TARGET as its first startup step and threw on bad values such as "", prod, or pr:0. With restart: unless-stopped, the container crash-looped and took down every analytics domain, not just the dbt mart readers. A pr:<N> target whose relations were dropped failed silently every cycle, and resolveDbtRelation logged on every call.

## Changes

- sync/src/redshift/dbt-relations.ts

- reportDbtTargetAtStartup logs the target. On a bad value it calls console.error naming the affected refreshes, returns null, and never throws. resolveDbtRelation still throws per call, so those refreshes fail through the existing per-domain allSettled and try/catch handling.

- preflightDbtRelations checks information_schema.tables for each PR-target relation and warns about missing ones. It is skipped for production and never throws.

- resolveDbtRelation logs each target and relation once per process.

- sync/src/analytics-worker/index.ts: uses the startup report, then runs the preflight without awaiting it, for PR targets when Redshift is configured. The preflight covers the Admissions Pipeline, program identity, Forecast, and SIS enrollment and staffing models.

- sync/src/redshift/admissions-forecast.ts: forecast models are exported as ADMISSIONS_FORECAST_DBT_MODELS, with no behavior change.

## Breaking changes

None. Production pins DBT_TARGET=production, which behaves as before apart from the reduced logging.

## Test plan

- [x] pnpm vitest run src/redshift src/analytics src/analytics-worker (1939 tests passed)

- [x] New tests: invalid targets "", prod, and pr:0 are reported without throwing; the relation is logged once; the preflight warns about missing relations, is skipped for production, and survives Redshift errors

- [x] Negative check: with the source changes stashed, the new tests fail

- [x] pnpm typecheck and biome

#2030 — fix(admissions): project Forecast V2 session3 explicitly and use userError for finite check (AERIE-2343) @marcusdAIy  approved

## Summary

Two Forecast V2 hardening items:

- GET /v2/admissions/programs/{id}/forecasts/current now builds session3 from declared fields only, with no ...row.session3 spread.

- The publish-time finite-metric check throws userError like its neighbours.

AERIE-2343

## Why it's needed

- The #1468 outage happened because stored session rows gained keys the closed response schema didn't declare, so every program returned 500 operation_response_schema_mismatch. session1 has since been projected explicitly, but session3 still spread the stored row. The next column added to storage would have brought the outage back.

- The finite-metric check in publishAdmissionsForecastV2 threw a plain Error. The surrounding validation uses userError, so worker logs and monitoring couldn't classify this rejection the same way.

## Changes

- chat/convex/publicApi/v2/domains/admissions.ts: new forecastSession3, which mirrors forecastSession1. It lists exactly the FORECAST_V2_SESSION_3_SCHEMA properties and reuses the existing stage-count and community projections.

- chat/convex/admissions/analytics/forecastV2.ts: throw new Error(…must be a finite number) becomes throw userError(…). The message is unchanged.

- Tests:

- publicApi/v2/admissions.test.ts: adds an undeclared key to stored session1/session3 (schema validation off in the test only), then expects 200 with the key absent from the response. Without the fix it returns 500.

- admissions/forecastV2.test.ts: the non-finite metric test now asserts the rejection carries a userError message. It fails against the plain Error.

## Breaking changes

None. The response shape is unchanged; it's now built field by field.

## Test plan

- [x] pnpm vitest run convex/admissions convex/publicApi/v2/admissions.test.ts convex/publicApi/admissionsDomainsHttp.test.ts (23 files, 644 tests)

- [x] Both new assertions fail without their source change

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2029 — fix(public-api): match edge-rewritten ETags for /dss and v2 conditional GETs (AERIE-2340) @marcusdAIy  approved

## Summary

Conditional GETs to /dss and to the v2 routes that use publicApiIfNoneMatchMatches now return 304 when the client echoes the ETag rewritten by the edge (W/"sha256-…-gzip").

AERIE-2340

## Why it's needed

When the edge compresses a response, it rewrites the origin's strong ETag into a weak one with an encoding suffix. /dss compared If-None-Match with strict equality, and the shared v2 helper stripped W/ but not the suffix. As a result, every client behind the edge re-downloaded the DSS documents on each poll (about 274 KB for the dictionary and 173 KB for enablement). This was reproduced on production 2026-09-23.

## Changes

- packages/contracts/src/public-api-v2.ts: publicApiIfNoneMatchMatches also strips a trailing -gzip, -br, or -zstd inside the quoted tag before comparing.

- chat/convex/publicApi/dss/http.ts: uses the shared helper instead of ===. It now also accepts W/ and comma-separated lists, as v2 already does.

- Tests:

- Helper unit cases cover edge-shaped tags for each encoding, plus non-matches for a different hash and a near-miss suffix.

- A /dss/{dictionary,enablement} route test checks that an edge-shaped If-None-Match returns 304.

## Breaking changes

None.

## Test plan

- [x] packages/contracts: pnpm vitest run src/public-api-v2.test.ts (24 pass)

- [x] chat: pnpm vitest run convex/publicApi/dss convex/publicApi/v2/http.test.ts convex/publicApi/agentContext app/api/skill app/api/openapi.json (41 pass)

- [x] Both new tests fail without the source change (/dss returns 200)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

- [ ] After deploy: GET https://edu-ops.klair.ai/api/dss with the echoed edge ETag returns 304

#2028 — fix(rhodes): align MCP milestone dates and tool text with API v2 (AERIE-2342) @marcusdAIy  approved

## Summary

Closes the three Rhodes MCP and API v2 presentation gaps from the release #1448 parity check:

- MCP milestone dates are now date-only, as in API v2.

- The stale "all 9" tool description is fixed.

- listDocuments now states in its description and output that it returns all document versions.

AERIE-2342

## Why it's needed

Agents comparing MCP and API answers saw mismatches even when the values agreed:

- 2026-03-30T03:54:41.435Z vs 2026-03-30.

- Contradictory "all 9" / "all 10" instructions.

- Document counts that differ because MCP lists every version while the API defaults to versions=latest.

## Changes

- chat/convex/rhodes/mcp.ts: getSite (milestones, buildoutMilestones) and getMilestoneWUSummary now normalize dueDate/completedDate with the same normalizeIsoDateOnly/normalizeUsDateOnly helpers as API v2's lifecycle milestones. A stored value that can't be parsed is passed through unchanged rather than dropped. Capacity and opening derivations still read the raw stored values.

- listDocuments output includes filters.versions: "all".

- chat/rhodes-worker/mcp-server/tools/views.ts: "all 9" changed to "all 10"; notes that dates are YYYY-MM-DD.

- chat/rhodes-worker/mcp-server/tools/documents.ts: the listDocuments description states that it returns every version and that API lists default to versions=latest.

- chat/convex/rhodesMcpParity.test.ts: new test covering timestamp, unparseable, and phase dates across getSite and getMilestoneWUSummary, plus the listDocuments versions marker.

The listDocuments default is documented rather than changed. API v2's latest-version projection spans tables and handles truncated or unavailable projections. Applying it inside a paginated MCP page would risk wrong counts, and driveAudit relies on the full list.

## Breaking changes

None expected. MCP milestone dates lose their time component, which API v2 already drops.

## Test plan

- [x] pnpm vitest run convex/rhodesMcpParity.test.ts convex/rhodesMcpMutationParity.test.ts convex/rhodes convex/agentRuns.test.ts lib/agent (32 files, 593 tests)

- [x] New test fails without the mcp.ts change (receives the raw ISO timestamp)

- [x] rhodes-worker: pnpm test (331 pass) and pnpm typecheck

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2026 — fix(public-api): return retryable 503 for authorization timeouts (AERIE-2900) @marcusdAIy  approved

## Summary

When Convex times out with "too many system operations" during Public API v1 authorization (API key validation or rate-limit consumption), the API now returns a typed authorization_unavailable 503 with Retry-After: 5, instead of an opaque internal_error 500 that is captured as an unexpected Platform Error.

AERIE-2900

## Why it's needed

A GET /v1/admissions/funnel/students request failed inside authorizeApiRequest before the route handler ran. Both nested calls (validateByHash, consumeRateLimit) are single indexed lookups or patches, so the timeout is transient platform load rather than a query defect. The caller got no signal to retry, and every recurrence would be triaged as a new unexpected error.

## Changes

- chat/convex/publicApi/http.ts: add withTransientAuthorizationTimeout, which wraps only the two authorization calls. A non-ConvexError whose message contains "too many system operations" becomes a retryable 503 authorization_unavailable. Add that code to the handleApiRoute capture exclusions, alongside the warehouse-unavailable codes.

- The match is scoped to the authorization step on purpose, not added to apiErrorFromUnknown. That way a route handler that hits the same execution limit (for example, from an unindexed scan) still returns 500 and is captured.

- chat/convex/publicApi/authorizationTimeout.test.ts: route-level tests. A timeout during authorization returns 503 with Retry-After and no errorEvents row. Any other authorization error still returns a captured 500.

## Breaking changes

None. This is a new 503 code for a condition that previously returned 500.

## Test plan

- [x] pnpm vitest run convex/publicApi (38 files, 575 tests)

- [x] New 503 test fails without the http.ts change (receives 500)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2189 — feat(rhodes-staging-sync): load the Rhodes audit log daily with redacted payloads (SURTR-1649) @kevalshahtrilogy  approved

## Summary

Adds raw_audit_log, the Rhodes change history (Convex auditLog, about 309k rows), to staging_education_rhodes. It's a full snapshot on its own daily schedule (additional_schedules, 05:13 UTC, entities: ["raw_audit_log"]); the hourly run skips it. Lambda memory goes from 1024 MB to 4096 MB. Translation version v10; v9 manifests stay replayable.

Linear: [SURTR-1649](https://linear.app/builder-team/issue/SURTR-1649) (follow-up to SURTR-1645)

## Why this shape

Measured against production on 2026-10-20:

- Full snapshot: 309,168 rows, 302 pages, 301 MB, about 5 minutes, 1.9 GB peak memory. That's too much to ride the hourly run (about 7 minutes already, 15-minute limit) and too much for the 1 GiB function, hence its own schedule and 4096 MB.

- Convex document_deltas (incremental) was built and rejected. It walks the whole deployment change log: 1,293 pages and 736 seconds for about 72 minutes of changes. That doesn't fit any hourly budget, and it would store about 150 Object Lock pages an hour.

Daily freshness is the trade-off. The other 31 tables stay hourly.

## Redaction

before/after are JSON-string snapshots of whole records. They're parsed into SUPER (before_value, after_value), with credential-shaped keys (password, secret, token, credential, login, authorization, cookie, signature, access code, API/private/encryption/access keys, key hash) set to [redacted], mirroring the Rhodes API's change-history rules. utilities also lose credential and payment fields, as in raw_sites. source_record carries the redacted strings; immutable S3 keeps the exact bytes, as for every other table. Over real production rows, redaction changed a handful of records, so this is needed.

## Validation

- uv run pytest: 262 passed. ruff check and ruff format --check are clean, and apply_ddl.py --dry-run renders.

- Real data: 8,000 production audit rows flatten with no errors and no unmapped fields; the full production extraction completes (309,168 rows).

## Rollout (production; each step mutates AWS/Redshift)

1. scripts/apply_ddl.py ddl/staging_education_rhodes.raw_audit_log.sql

2. Release; CD deploys the Lambda (4096 MB) and the new audit-log EventBridge rule.

3. Run one manual execution with params.entities = ["raw_audit_log"] and confirm the ledger count matches the source.

4. GRANT SELECT ON ALL TABLES IN SCHEMA staging_education_rhodes to edu_reader_user, edu_raw_reader_user, full_reader_user, full_raw_reader_user and "yibin.long".

## Business Value

Completes the "all of Rhodes in SQL" ask for the DSS registry seat: change history becomes queryable next to the rest of the dataset, refreshed daily, without exposing credentials the API redacts.

## Manual Effort Estimate

About 1 day of focused work: measure snapshot versus deltas against production, port the API's redaction, schedule and memory changes, tests. Proposed by Claude; Keval to confirm or adjust.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2188 — fix(quickbooks): map five approved shared-book Classes to Schools @ashwanth1109  approved

## Business Value

Assign five approved shared-book QuickBooks Classes to Financial District, Upper West Side and Carrollton so Finance can report their 293 postings ($199,286.29 signed QB P&L) against the correct Schools while retaining original source amounts and traceability.

## Change

Add five exact realm/Class assignments through the existing governed financial crosswalk. Check accepted source identities, active canonical Schools and their single approved Programs, conflicts with Aerie/model/current financial assignments, and the reviewed posting population before writing. Preserve all 36 existing policy rows. An identical reapplication is a no-op; partial/conflicting applications fail atomically.

Approval was forwarded from the user's side chat on 20 October. The policy records user approval without claiming separate Finance approval. Founders Hub, Greenwich, HISD, unused variants and Aerie ontology links stay outside this change.

## Validation

- 203 Core-runner tests passed; 72 existing opt-in integration tests skipped. Scoped Ruff passed.

- Candidate SQL applied before merge. An intentional rollback probe preserved all prior rows and removed the temporary procedure; the real application added five rows (41 total), and a second complete application preserved all rows and metadata exactly. Owner/ACL unchanged.

- Core plus all five downstream refreshes succeeded before merge with failure notifications suppressed. All 293 postings resolve correctly; all source business values and the other 368,179 school assignments remain unchanged. The 194 non-headcount source lines moved to School detail; 99 raw headcount postings now support existing XO-priced School calculations. See the [validation record](https://github.com/AI-Builder-Team/Surtr/blob/1074d0e09fe20355d51991c7c036b599e9c8c218/pipelines/runners/quickbooks-core-tables/SHARED_BOOK_SCHOOL_POLICY_2026_10_20.md#live-validation-20-october-2026).

## Deployment order

Stacked after PR 2186, whose scope-aware publication is already live-validated. PR 2175 has merged. The candidate is a warehouse policy migration; Core runtime and shared infrastructure do not change. Existing Core/mart writers perform the supported refreshes.

## Implementation Effort

Approximately 1 engineer day without AI assistance, including identity/conflict checks, guarded migration, tests, operational validation and source/downstream reconciliation.

## Linear

https://linear.app/builder-team/issue/SURTR-1648/map-approved-shared-book-classes-to-financial-district-upper-west-side

#2186 — [SURTR-1647] Retain unclassified QuickBooks P&L postings @ashwanth1109  approved

## Business Value

Finance can inspect accepted QuickBooks P&L postings without a School mapping or visible School detail bucket. Preserve their source amounts and traceability while keeping the existing School, enrollment and XO-priced calculation semantics.

## Change

Publish paired unclassified / quickbooks_posting rows after School calculations, with source-qualified keys and detail_key = Core.posting_id. Retain classless lines, account exceptions, credits, zeros and raw QB headcount. Sum original Core precision before rounding aggregate totals; round detail amounts to cents. Unclassified School calculation fields remain NULL.

Validate private candidates before target replacement, including explicit rejection of missing source/display/aggregate amounts. The atomic procedure and independent runner checks cover source completeness, identity/amounts, scope overlap, parents, aggregates and invented School measures. NULL-safe comparisons and separate missing-source counts prevent arithmetic from concealing missing values. Existing School guards remain scoped to School rows. The SQL deployment helper preserves literals while fitting the complete Data API batch limit.

## Deployment order

PR #2175 is merged; this PR targets main. The schema from #2185 and consumer changes in Aerie #2006 and Klair #3876 are deployed. The native stack preserves mapping PR #2188 above this producer change; merge #2186 first.

The candidate Lambda and primary procedure are deployed and live-validated before merge. CDK targeted only Pipeline-mart-aerie-education-financials-refresh-prod --exclusively; CloudFormation confirmed UPDATE_COMPLETE and [1/1]. Owners and grants were preserved.

## Validation

- 756 regular runner tests passed; both opted-in complete-procedure Redshift fault cases passed separately. Scoped Ruff passed.

- Quiet Core alignment and all five downstream refreshes succeeded on the latest ontology generation before the baseline.

- Candidate execution scope-pr4-null-candidate-20261020T122629Z succeeded: 81,571 unclassified detail rows and 2,404 summary rows. All 77,812 unmapped source postings reconcile exactly to Core, and all nine accounting/scope checks pass.

- All ten business fingerprints match baseline: both scopes in the P&L marts, Unit Economics, all QTD marts and enrollment findings.

- Full-procedure probes reject a NULL candidate before any target DELETE and a corrupted amount after publication. Both marts retain identical full-column fingerprints; installed procedure body/owner/ACL are unchanged and temporary clones are rolled back.

- Execution references, rollback statement IDs, reconciliation and earlier repeat-refresh evidence: [validation record](https://github.com/AI-Builder-Team/Surtr/blob/a0ffcc1068d98a6eaca5f8cda9c83d665ff4dd4d/pipelines/runners/mart-aerie-education-financials-refresh/UNCLASSIFIED_PUBLICATION_VALIDATION.md).

## Implementation Effort

Approximately 2 engineer days without AI assistance, including SQL implementation, regression coverage, deployment safeguards and live reconciliation.

## Linear

https://linear.app/builder-team/issue/SURTR-1647/publish-unclassified-quickbooks-pandl-postings-without-changing-school

#1999 — Fix Physical Forecast by-level totals for Alpha Austin @vvp-trilogy  approved

## Summary

- ingest the level-and-grade forecast operand mart and retain canonical student levels

- publish physically attributed January by-level forecasts for Alpha Austin and Alpha High

- fail closed when physical level rows are missing or do not reconcile within the independent-rounding policy

- select physical level rows with the physical headline while preserving Program mode

## Validation

- pnpm --dir packages/contracts exec vitest run src/admissions-forecast-v2-physical.test.ts --maxWorkers=1

- pnpm --dir sync exec vitest run src/redshift/admissions-forecast.test.ts src/redshift/dbt-relations.test.ts --maxWorkers=1 --silent

- pnpm --dir chat exec vitest run components/dashboards/admissions/forecast/v2/__tests__/forecast-v2-view.test.tsx --maxWorkers=1

- pre-commit: Convex paths, Biome, sync typecheck, Chat typecheck

Closes #1997

#2175 — fix(reports): publish QTD reports with approved Finance models and explicit data gaps @ashwanth1109  changes requested

## Business Value

Schools with resolved enrollment can receive QTD reports using the approved Finance assumptions even when other students lack School mappings or QuickBooks budgets are incomplete. Missing budgets remain visible data gaps; actuals and independent unit-model comparisons remain available.

## Implementation

- Publish unresolved-enrollment findings and coverage atomically with financial marts. Retain source observations, restore resolved students automatically, and keep ambiguous identity and other non-budget gates blocking.

- Capture the approved Finance sheet's 31 model definitions and 12 canonical School assignments, including Highland Park's new model and the 1.15 staffing burden. Preserve effective history and unrelated Class assignments. The three QTD detail consumers now share the governed reference used by Tables 2/3.

- For the 42 approved October 16 Schools, permit missing QuickBooks budgets in every category, including Staffing, Guide and Lead Guide. Missing budget, variance and variance-percent cells display Unavailable, with an exact Data gaps to fix category list.

- Process up to ten Schools concurrently with independent clients, a fenced batch lease, API pacing, saved research and approved-text checkpoints, isolated School failures and review-only delivery. Version the renderer so a format repair can rebuild documents while retaining reviewed inputs and narratives. Fit unavailable labels at readable sizes.

- Preserve comparison categories and student units, require the claimed per-student measures, review every narrative field against full evidence, and reject incomplete or contradictory audit approvals. Keep adjacent per-student and School-total body claims on their own units.

- Apply the approved exact Novatio account 162 transaction-fee mapping using accepted source-ledger evidence. Idempotent retries inspect current state separately from retained history and preserve the original reviewed capture and marker.

- Keep warehouse application explicit: private backups, exact Class fingerprints and history verification, checks that survive Python optimization, and post-lock catalog guards before replacement DDL. Install the reference publisher, temporary migration, privileges and publication call in one transaction; preserve owners and ACLs.

## Validation before the October 20 review fixes

- Local suites: 524 report tests, 592 financial tests, 55 unit-economics tests and seven Novatio repair tests passed. Changed Python files pass Ruff formatting/checks. The model-consumer SQL tests execute all 31 approved fixtures. Every CI test/lint job on 45423ad7 passed; automated review of the latest commit is separate.

- Live reference publication verified all 31 exact definitions, 12 Schools and 42 reviewed Class identities. Seven superseded assignments remain historical, unrelated assignments and rendering rules are retained, and repeat publication adds no policy history. Annual staffing/program model amounts reconcile to the approved reference across all 42 positive-model Schools in the detail marts.

- QuickBooks Core e81bd02b-44a1-4d73-959d-439c9d476f20 and the required financial, QB-budget, unit-economics and per-student runs succeeded. Financial run 51afec55-12e9-4528-a6ba-5eb5c8a5ea37 passed every QTD sibling postcheck.

- Final 34-School batch 1b08e6a0-c7cc-42f8-b611-7127c0b3a3f1 succeeded with no remaining failures. Each report uses the new assumption version and 1.15 burden. Native document readback matches its payload, immutable PDFs pass validation, and the review digest was sent only to Ash. The prior 17 assumption-version-v1 documents remain historical copies. Provider/audit failures were recovered from checkpoints, with targeted narrative corrections reviewed before publication.

- Hardened helpers passed live with Python optimization enabled: three consumer definitions and enrollment DDL installed under locked catalog guards, an atomic reference publication passed exact-identity/history/idempotency verification, and repeated Novatio calls preserved policy. Owner/ACL parity was verified.

- Deployed only Pipeline-school-performance-reports-prod with --exclusively; CDK confirmed [1/1], and CloudFormation events confirmed UPDATE_COMPLETE. Candidate task revision 59 contains the reviewed runtime source. Fresh Charlotte validation 4dbf996d-416d-4027-bbcf-a0bfc826a24c succeeded with an approved narrative, exact native readback and validated PDF; completed 34-School artifacts were retained.

- All manual runs suppress failure notifications, and automatic downstream links inherit that preference. Logs/run records and operational alarms remain enabled. The unrelated Q22 consumer still rejects run_options; it is not a report input.

Eight Schools remain blocked only by enrollment inputs: Bethesda, Boston Suburbs, Houston Heights, Fort Lauderdale, Marin County, Orlando, San Juan PR and Tampa. Their model assignments are resolved; missing budgets no longer block this approved October 16 population.

## Review fixes — 20 October 2026

- Persist the Finance assumption version on all three QTD sibling marts, reject legacy or mixed versions in report reads, and migrate the existing Aerie P&L model consumer to the same approved reference, including Highland Park.

- Require the complete approved 31-model set, preserve unrelated policy versions, re-audit stale corrections regardless of the retained audit checkpoint, retain per-student budget evidence, and reject absent/duplicate enrollment telemetry.

- Check exact installed procedure sources and privileges before deployment transactions commit. Finance publication verifies approved values, preserved policy/history/rules and repeat-call idempotency, then removes its temporary procedure in the same transaction.

- Strengthen enrollment fixtures with exact eligible observations and ineligible cases; correct operator documentation and missing-assumption diagnostics. Three older claims already match the code: rejected audit aggregation, distinct student counting and null variance-percentage enforcement.

Validation for aeb7e86c: 632 financial, 540 report and 64 unit-economics tests passed; changed Python files pass CI-pinned Ruff 0.15.22 and all three deployment helpers pass offline dry runs. The helper-import follow-up also passed 27 targeted catalog/deployment tests. The Redshift reserved-alias repair passed the 64-test unit-economics suite and the live atomic publication.

Live validation on October 20:

- Applied the P&L and three QTD definitions with exact before-commit source/owner/ACL checks. The Finance helper verified 31 exact model definitions, 12 Schools, 42 Class identities, preserved policy/history/rules and repeat-call idempotency in one transaction. Its initial reserved-alias failure left all four reference/policy tables unchanged; the corrected retry succeeded.

- Deployed only Pipeline-mart-aerie-education-financials-refresh-prod and Pipeline-school-performance-reports-prod, each with --exclusively and [1/1]. Both stacks reached UPDATE_COMPLETE; CloudFormation events were retained. The financial Lambda source matches the candidate exactly; report task 61 uses the image whose staged reader/insights sources match the candidate.

- Financial run 27646f18-e912-4689-88df-1ff2a0e35c46 succeeded, including all three QTD postchecks. All 21,056 QTD rows across 64 Schools carry the approved v2 assumption version. All 6,948 model staffing-detail rows use 1.15. Highland Park's nine-student model now publishes annual tuition of $540,000, Programs of $90,000 and total staffing of $224,250.

- The reader accepts Highland Park's coherent live six-mart publication and rejects an in-memory legacy-version substitution in each QTD sibling. The run retained skip_failure_notification=true, produced no failure notification and recorded 1,433 historical enrollment exclusion observations / 11 current distinct students with has_unresolved_students.

BLOCKER — end-to-end report generation: the current cutoff is October 20. Thirty-eight Schools have missing required budgets (tuition, other revenue, Staffing, Facilities or Guide roles); the other four lack positive enrollment. Ash explicitly chose to retain the October 16 exception and leave report validation blocked. No report execution or report email was attempted. The prior live report-generation evidence above applies to the previous candidate.

CI on aeb7e86c: all seven CI jobs pass, including the full runner tests. The automated-review job completed its analysis but failed to post the review with HTTP 401 (Bad credentials); its saved artifact contains additional findings.

Merge decision on October 20: Sanket approved exact commit aeb7e86c. Ash explicitly authorized merging that approved commit while accepting the blocked end-to-end report validation and the additional unposted review findings. The October 16 reporting policy remains unchanged. Disclosed outstanding findings include the reproduced mixed-unit headline validation bug and the unqualified temporary-table cleanup risk. A tested headline fix is retained separately and is not included in this approved commit.

## Implementation Effort

Approximately four engineer days to implement, test and validate by hand without an AI agent.

## Linear

[SURTR-1640](https://linear.app/builder-team/issue/SURTR-1640/publish-resolved-school-financials-with-unresolved-enrollment-findings)

#2023 — fix(rhodes): redact unexpected approval preparation errors @ashwanth1109  approved

## Business Value

When document approval preparation fails unexpectedly, users receive a safe retry message instead of internal exception text. Expected document override validation remains readable and proposals remain pending for a later authorized attempt.

## Implementation Effort

Estimated 1–2 engineering hours for an average engineer to investigate, implement and verify without AI assistance.

## Change

- Replace raw exception fallback in the new approval preparation catch with a safe message; retain userErrorMessage for explicit user errors.

- Mark document override validation failures as user errors so existing title/topic and unsupported-field messages survive the boundary.

- Cover unexpected failures, coded errors, missing proposals, and worker-secret rejection through the real registered action with typed internal-call fakes.

## Validation

- Six approval error regression tests pass under Node 22.

- Full affected mutation parity suite: 108 passing tests. Chat typecheck passes.

- Biome passes on all three changed files.

- No live approval, Due Diligence writeback or external mutation was executed by this validation.

## Linear

[AERIE-2937](https://linear.app/builder-team/issue/AERIE-2937/release-aerie-main-to-production-20-oct-2026)

Addresses the approval-error finding on release PR #2021. The two warehouse/checklist findings have separate verification evidence in their original review thread.

#2000 — Add Finalsite Shadow Day checklist fallback with provenance @vvp-trilogy  approved

Closes #1998.

Students without a qualifying Shadow calendar appointment can now resolve a Shadow Date from the completed, exact normalized Schedule Shadow Day checklist item. Calendar selection remains authoritative; checklist provenance travels through dbt, both worker read contracts, Convex storage, and the admissions record detail. Calendar status, history, and pipeline stage rules remain independent.

## Testing contract

### What this PR delivers

An admissions analyst can see the best available Shadow Date for a student missing from the appointment feed and identify checklist fallback evidence without interpreting it as attendance.

### Who uses it and where

Authorized Admissions Pipeline readers, in the enrollment record detail. The public admissions API does not receive the new provenance field.

### Conditions needed

- A dbt build including checklist staging, shared Shadow resolution, and downstream marts, followed by an analytics refresh. Existing Convex records without provenance remain readable.

- Test records with calendar plus checklist evidence, checklist-only evidence, cancelled appointments, duplicate checklist items, incomplete items, override-only items, malformed/implausible timestamps, and no evidence.

- The Surtr Gateway copy must expose shadow_date_source before Gateway-mode publication. Legacy Redshift reads use the new mart column directly; missing Gateway columns fail closed.

### Expected behavior and examples

- A qualifying calendar visit wins over any checklist date and retains its status/history.

- A completed Schedule Shadow Day timestamp of 2026-04-25T04:00:00Z resolves to 2026-04-25 only when no qualifying calendar appointment exists. The detail labels it Source: Finalsite Schedule Shadow Day checklist (fallback).

- Duplicate standard items use the latest valid completion. The documented sanity policy accepts timestamps from 2014-01-01 through the warehouse's current instant, inclusive; invalid, earlier, and future timestamps are ignored. Timestamp-to-date conversion uses UTC.

- Override, consent, and other checklist tasks cannot supply the fallback. A checklist date does not fabricate status, appointment history, scheduled flags, or attendance.

- Old records display their existing date with no invented source; public API DTOs continue excluding internal provenance.

### Validation

- Focused worker query/Gateway/refresh tests, Convex persistence/query tests, React detail tests, and public API projection tests.

- dbt parse passes. An isolated Redshift build of both downstream Pipeline and Forecast marts and their dependencies passes (50 models/seeds), as do both deterministic units and the live provenance/history and lead-null assertions (4 tests). Both marts retain the new source field. Temporary pr1998_ objects were removed after validation.

- Warehouse comparison: 446 calendar-derived records unchanged (date, status, scheduled flag, history); 44 additional checklist-derived dates. The referenced Charlotte case resolves to 2026-04-25, source schedule_shadow_day_checklist, null status/history, and false scheduled flag.

- Chat, Convex, and Sync type checks pass.

- Architecture boundaries, Convex read bounds, and test-runtime routing pass.

- First full CI dbt test run: 817 pass, 12 warnings, one unrelated live-source race in assert_sis_enrollment_reason_fields_survive_staging. All six differing SIS records were ingested at 16:10:53 UTC, after the staging snapshot built at 16:07:44 UTC. The unchanged SIS staging model copies these reason columns directly. Fresh current-head CI on 2026-10-20 passed: 818 dbt tests passed, 12 warnings, zero errors (830 total). All application CI checks also passed; no assertion was weakened.

### Limits and unanswered questions

- The earliest accepted timestamp is an explicit implementation policy (2014-01-01); the draft requested a sanity window without supplying its bounds.

- The externally owned Surtr copy needs the additive column before enabling Gateway-mode reads of this contract.

#2185 — [SURTR-1646] Prepare P&L reporting scope for unclassified transactions @ashwanth1109  approved

## Business Value

Establishes the minimal contract for unclassified QuickBooks transactions to be queryable in Redshift while existing Aerie readers preserve school-only reporting. This is PR 1 of the four-PR rollout.

## Changes

- Add only reporting_scope and amount_basis to each mart: four new columns total, with school / school_presentation defaults.

- Prepare nullable school/program compatibility from both legacy and base-DDL schemas. Required compound-sort-key columns use guarded physical-key preparation/restoration around the atomic column/value migration; OIDs, permissions and key order are preserved. The existing writer and runner still require real school context, and runtime publication remains school-only.

- Reuse existing detail references and Core for source amounts, mapping flags and lineage. Reconcile the earlier larger live proposal by dropping its other 22 untouched metadata columns after consumer/dependency checks, with guarded values/privileges, atomic application and RESTRICT.

PR 2 protects existing Aerie pages, consolidated queries, API readers, transaction drill-downs and exports with explicit reporting_scope = 'school' filters. The series includes no dedicated Unclassified page, feature switch or new unclassified API/export endpoints.

## Validation

- 595 affected-runner tests passed; changed-file Ruff/format checks passed. Base-DDL Redshift fixtures passed upgrade, exact row/catalog preservation, idempotency and legacy-insert checks; an injected failure proved schema/value rollback and original-sort-key recovery. See the review follow-up in REPORTING_SCOPE_VALIDATION.md.

- Final reduced schema applied: ed2bb9f6-52e1-477c-9c86-95609042f122. Existing values across eight outputs, table OIDs/owners/ACLs and runtime definitions were preserved by the migrations.

- Pre-merge live validation passed: user-approved Core refresh e43567e3-8921-4f82-9e95-c9b3612b8905 and all five downstream consumers succeeded with notification suppression preserved. Financial run 02e98896-ecd3-4493-b635-c6aec9ebd9f1 published 18,350 breakdown and 244,921 detail rows in school scope.

- Identity, coverage, FK, cost reconciliation, annualization, Finance denominator and all QTD checks passed. Transaction-detail business values are unchanged; student/model outputs refreshed newer Finalsite/XO observations. Execution IDs and source-change comparisons are recorded in REPORTING_SCOPE_VALIDATION.md.

## Review follow-up (e0a03288)

- Persist and replay each exact Data API request with its ClientToken. Evidence updates now use fsync and atomic replacement; every post-submission storage failure blocks follow-up recovery DDL, including terminal-status reconciliation.

- Reject a fresh run with an incomplete/changed original compound sort key before DDL. Require proven full column-grant visibility before replacement/cleanup, and repeat that proof under migration locks; no permissions are granted.

- Validate scope/basis values on both marts inside the locked migration transaction. The unchanged writer uses validated defaults; the future scope-aware producer must validate values at publication. Arbitrary external INSERTs are not schema-enforced enums in Redshift.

- 656 affected-runner tests passed, including 89 migration-helper tests; changed-file Ruff/format checks and diff checks passed.

- Fresh read-only live validation passed: production preflight, both mart value guards, same-statement lost-response replay, terminal evidence-failure handling, and rejection of unproven grant visibility for simulated replacement. The complete legacy sort key remains unchanged. These follow-up checks submitted SELECTs only; no production DDL, runtime procedure deployment, or pipeline invocation occurred. Original full pipeline acceptance is recorded above; supplemental statement IDs and details are in REPORTING_SCOPE_VALIDATION.md.

## Implementation Effort

Approximately 1 engineer day without AI assistance for contract design, guarded migration/reconciliation, regression coverage and live warehouse validation.

## Linear

https://linear.app/builder-team/issue/SURTR-1646/prepare-pandl-reporting-scope-contract-for-unclassified-quickbooks

#2011 — fix(rhodes): return readable failure when approval prepare throws (AERIE-2908) @marcusdAIy  approved

## Summary

approvePendingMutation now catches errors thrown while preparing an approval and returns a structured { status: "failed", toolName, error } result with the readable message, instead of letting the error escape the Convex action and get masked as [Request ID: ...] Server Error.

AERIE-2908

## Why it's needed

A driveUploadFile approval on the Rhodes Mutation Card failed with only a masked Server Error. The dispatch step already converts throws into a structured failure, but the prepare step (_preparePendingMutationApproval) did not, so override-validation, capability, and fallback-session errors reached the user as an opaque message with no recovery hint.

## Changes

- chat/convex/rhodes/mcp.ts: wrap the prepare runMutation in a try/catch that returns a failed result using userErrorMessage(error) ?? error.message. Add the _getPendingMutationToolName internal query so the failed result carries the canonical tool name. If the pending row doesn't exist, the original error is rethrown.

- The pending row is intentionally left pending, not patched to failed. The prepare handler treats permission failures as "row stays pending". Marking it failed here would let an unauthorized approver terminally fail someone else's proposal. The prepare mutation rolls back, so no partial state is written.

- chat/convex/rhodesMcpMutationParity.test.ts: the registerDocument override-change cases now assert a readable failed result and that both rows remain pending.

## Breaking changes

None. Callers already handle status: "failed" from the dispatch path. The worker's approve route returns it as a 400 JSON error.

## Test plan

- [x] pnpm vitest run convex/rhodesMcpMutationParity.test.ts convex/portfolio/backupSites.test.ts (143 passed)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2010 — fix(financials): return null annualized on forecast-only P&L breakdown API rows (AERIE-2905) @marcusdAIy  approved

## Summary

GET /v1/financials/marts/agg-school-pl-breakdown no longer returns a 500 for the whole page when a school-year row has a total but no annualized figure yet. Those rows now come back with annualized: null.

## Why it's needed

AERIE-2905. The shared row mapper threw on a null annualized, so one forecast-only school-year row (seen in production for line 60211, period 2026) failed every row on the page. Only the API reads school-year periods; the dashboard breakdown queries are quarter-only.

## Changes

- chat/convex/finance/dashboards/financialLive.ts: split the field mapping so the API row mapper (mapAggBreakdownApiRow) passes a null annualized through. The dashboard mappers (mapAggBreakdownRow, mapAggConsolidatedBreakdownRow) still throw on null, and a malformed non-null value still fails loud everywhere.

- chat/lib/public-api/openapi.ts: AggSchoolPlBreakdownRow.annualized is now nullable (still required).

- Tests: mapper unit tests for the null and malformed cases, an HTTP route test where one of two rows has a null annualized (returns 200 with both rows; it returned 500 before the fix), and a schema assertion.

## Breaking changes

annualized on AggSchoolPlBreakdownRow can now be null. Before this, those requests failed with a 500, so no client was receiving a number for these rows.

## Test plan

- [x] pnpm vitest run convex/finance/dashboards/ convex/publicApi/financialsHttp.test.ts lib/public-api/__tests__/openapi.node.test.ts (495 passed)

- [x] Confirmed the new route test fails with a 500 when the API mapper is pointed back at the strict mapper

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2009 — fix(agent): capture expected Flue gateway outcomes as expected_outcome (AERIE-2903) @marcusdAIy  approved

## Summary

Flue gateway failures that are already classified as transient or capability-unavailable are now captured with disposition: "expected_outcome" and the gateway code as outcomeCode, instead of defaulting to unexpected.

## Why it's needed

AERIE-2903. The gateway catch block captured every 5xx gateway error with the default unexpected disposition, so known upstream timeouts, unreachable Rhodes/REBL3, and not-configured capabilities showed up in the error inbox as unexpected failures alongside real bugs.

## Changes

- chat/convex/agentRuns/http.ts: when classifyGatewayError returns anything other than unexpected_failure, pass disposition: "expected_outcome" and outcomeCode: <gateway code> to captureConvexBoundaryError. unexpected_failure captures are unchanged.

- chat/convex/agentRuns.test.ts: assert the disposition/outcome code on the transient (unreachable Rhodes) and capability-unavailable (misconfigured Rhodes MCP URL) captures, and that a malformed REBL3 response (gateway_upstream_error) is still captured as unexpected with no outcome code.

Note: capability_unavailable includes rhodes_mcp_misconfigured, so a deploy misconfiguration is now recorded as an expected outcome too (still captured, still 503), per the ticket.

## Breaking changes

None. Response status codes and payloads are unchanged; only the captured event's disposition changes.

## Test plan

- [x] pnpm vitest run convex/agentRuns.test.ts (118 passed)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#2008 — fix(portfolio): show a scoped not-found state when the workbench site slug no longer resolves (AERIE-2916) @marcusdAIy  approved

## Summary

When the site slug no longer resolves (renamed or removed site, stale bookmark, mistyped link), the Portfolio site workbench now shows a scoped "Site not found" message. Before, it crashed the whole route with an opaque "Server Error" and captured an unexpected Platform Error.

Fixes AERIE-2916.

## Why it's needed

For an unknown slug, rhodes/portfolioWorkbench:getSiteWorkbench threw a plain new Error("Site not found"). Convex redacts that to "Server Error" on the client. The reactive query then threw during render, fell through to AerieRouteErrorFallback, and was captured as an unexpected route_error.

## Changes

- chat/convex/rhodes/portfolioWorkbench.ts: getSiteWorkbench returns null when no site matches the slug. The permission check still runs first and still throws for users without site-detail read access. WorkbenchData was already NonNullable<...> of the return type, so consumers are unchanged.

- chat/components/dashboards/portfolio/portfolio-rhodes-workbench.tsx: PortfolioRhodesWorkbench renders a scoped "Site not found" state, naming the slug, when the query returns null. Nothing reaches the route error boundary, so nothing is captured.

- Tests:

- chat/convex/rhodesPortfolioWorkbench.test.ts asserts an unknown slug resolves to null. Existing call sites go through a small present() helper now that the return type is nullable.

- portfolio-rhodes-workbench.test.tsx asserts the scoped not-found UI.

## Breaking changes

None. getSiteWorkbench has one caller (PortfolioRhodesWorkbench), which now handles null.

## Test plan

- [x] pnpm vitest run convex/rhodesPortfolioWorkbench.test.ts components/dashboards/portfolio/__tests__/portfolio-rhodes-workbench.test.tsx components/dashboards/portfolio/__tests__/site-detail-page-rhodes-tabs.test.tsx (150 passed before the test-helper refactor; the Convex file was rerun after it: 69 passed)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#3876 — fix(data-api): distinguish school and unclassified P&L scopes @ashwanth1109  approved

## Business Value

Help Finance queries keep existing school P&L totals separate from unclassified QuickBooks postings when both appear in the same warehouse marts. Agents receive the scope, snapshot, and accounting-basis rules through Klair's live /api/v1/meta guidance.

## Changes

- Require explicit school or unclassified scope for the breakdown and transaction-detail marts, including snapshot selection and summary/detail joins. A known school identity on an account exception does not select school reporting scope.

- Distinguish school_presentation, quickbooks_posting, and xo_priced amounts. Preserve school presentation residuals while excluding them from raw QB posting totals; avoid double-counting account/subtotal rows, periods, or the unmapped monthly summary.

- Update school P&L, transaction-detail, and facilities-rent guidance. Add an unclassified investigation workflow covering unpublished/empty scope, source traceability, signed amounts, Finance-approved Central activity, and unavailable school/model/per-student measures.

The repository audit found no fixed SQL readers or query templates for these two marts. This updates discovery guidance; /query continues executing caller-supplied read-only SQL. The thin installed skill reads guidance live, so its pack and version remain unchanged.

## Validation

- Full MCP suite: 73 suites / 1,108 tests passed (npm test -- --runInBand).

- npm run typecheck passed using the package's committed npm lockfile.

- Changed-file ESLint and Prettier checks passed; git diff --check passed.

- Existing API route/OpenAPI contracts, scoped DB profiles, and skill-version checks pass.

## Rollout

PR 3 of the four-PR series. Shared schema: [Surtr #2185](https://github.com/AI-Builder-Team/Surtr/pull/2185), already applied and live-validated. Aerie school readers: [Aerie #2006](https://github.com/AI-Builder-Team/Aerie/pull/2006), merged.

Merging changes under this MCP package into main triggers its deployment workflow. Verify the returned /api/v1/meta guidance after that deployment, and deploy all reader changes before PR 4 publishes unclassified rows. Warehouse publication remains unchanged by this PR.

## Linear

[KLAIR-3611](https://linear.app/builder-team/issue/KLAIR-3611/clarify-reporting-scopes-in-education-pandl-query-guidance)

## Implementation Effort

About 2–3 hours for an engineer working without AI: audit consumers, reconcile the warehouse contract with existing guidance, update the workflows, and validate the API contracts and MCP suite.

#2006 — fix(finance): keep existing P&L readers in school reporting scope @ashwanth1109  approved

## Demo

<img width="2624" height="1636" alt="image" src="https://github.com/user-attachments/assets/538d5339-8103-44fc-b73a-254b6e11a084" />

## Business Value

Keep existing school and consolidated P&L results, drill-downs, and exports stable when Surtr begins publishing unclassified QuickBooks transactions in the same marts. Finance will inspect unclassified amounts through Redshift; this change adds no UI, feature flag, endpoint, or export.

## Changes

- Restrict every existing breakdown/detail mart reader to reporting_scope = 'school', including per-student divisors and bounded public API readers.

- Resolve latest P&L snapshots within school scope, including the snapshot pinned into v2 detail cursors.

- Preserve selected columns, response/export shapes, filters, aliases, pagination, and calculations. Document school scope in the existing raw-row API descriptions.

## Rollout

PR 2 of the four-PR rollout. Depends on the schema in [Surtr #2185](https://github.com/AI-Builder-Team/Surtr/pull/2185), whose candidate migration is already deployed and live-validated. Deploy this Aerie reader change after that schema is present and before PR 4 publishes unclassified rows. Klair reader guidance (PR 3) can proceed alongside this PR.

## Validation

- 325 tests pass across 9 focused reader, API, authorization, P&L shaper/export, and OpenAPI test files.

- Chat and Convex TypeScript checks pass (pnpm --dir chat typecheck).

- Changed-file Biome, Convex path, and test-runtime checks pass.

- Read-only Redshift comparisons passed for 9 generated reader queries: identical row counts and zero rows added/removed versus the original SQL. The existing export retained 5,010 rows and a populated cost cell retained 837.

- The same queries preserved school results against CTE-only fixtures with unclassified rows carrying the same school keys, NULL annualization/divisors, and a newer snapshot. No unclassified data was written to the warehouse.

## Linear

[AERIE-2926](https://linear.app/builder-team/issue/AERIE-2926/keep-existing-pandl-readers-in-school-reporting-scope)

## Implementation Effort

About 3–4 hours for an engineer working without AI: trace readers and API cursor behavior, add the scope filters, write regression coverage, and verify the queries against Redshift.

#2004 — fix(chat): reload for stale webpack runtime missing-module TypeErrors (AERIE-2919) @marcusdAIy  approved

## Summary

Main App error boundaries now treat the webpack runtime's "missing module factory" TypeError (Cannot read properties of undefined (reading 'call') and its Safari/Firefox wordings) as a stale bundle. The page reloads once, the same as a ChunkLoadError, instead of showing "Something went wrong" and capturing an unexpected Platform Error.

Fixes AERIE-2919.

## Why it's needed

A tab that loaded before a deploy can fetch a new chunk whose module ids no longer match its in-memory webpack runtime. The runtime finds no factory and throws this TypeError instead of a ChunkLoadError. isChunkLoadError() (from AERIE-2826) only recognized the ChunkLoadError / "Loading chunk … failed" forms. This signature has produced 12 events across 4 sessions and 3 users, including after #1822 shipped.

## Changes

- chat/lib/chunk-load-recovery.ts: isChunkLoadError() also matches a TypeError with one of the three browser wordings of the missing-factory message, but only when the top stack frame is the webpack runtime: __webpack_require__, or Next's /_next/static/chunks/webpack(-hash).js. The message alone is too generic, so the same TypeError thrown from application code (with the runtime further down the stack, or with no stack) still captures normally. Both AerieErrorBoundary and AerieRouteErrorFallback already route matches through reloadForStaleChunk(), including its 60s single-reload cooldown, so their code is unchanged.

- Tests:

- chunk-load-recovery.browser.test.ts covers the Chrome, Safari, Firefox and dev-runtime forms, plus negative cases: an app-code top frame, no stack, and a different property name.

- aerie-error-boundary.test.tsx and aerie-route-error-fallback.test.tsx assert the "Loading the latest version…" reload path with no capture.

## Breaking changes

None.

## Test plan

- [x] pnpm vitest run lib/__tests__/chunk-load-recovery.browser.test.ts components/__tests__/aerie-error-boundary.test.tsx components/__tests__/aerie-route-error-fallback.test.tsx (15 passed)

- [x] typecheck-chat and biome (pre-commit)

- [ ] After deploy: no new Main App route_error events for this fingerprint

#2003 — fix(rhodes): classify work unit doc-gate approval rejections as expected outcomes (AERIE-2899) @marcusdAIy  approved

## Summary

When a moderator approves a "complete work unit" proposal whose required documents aren't registered yet, the Rhodes Mutation Card now records an expected outcome (rhodes.work_unit.required_documents_missing) instead of an unexpected Platform Error. It also shows the clean doc-gate message. The completion gate itself is unchanged.

Fixes AERIE-2899.

## Why it's needed

updateWorkUnitStatus blocks completion until the work unit's producesDocTypes are registered, unless skipDocGate is passed. That rule works as designed, and the public API already classifies the same message as a conflict. But the Rhodes approval path returned it to the card as a plain Error, so normalizePlatformErrorCapture recorded it as unexpected. Every completion approval on a work unit with missing documents would keep opening new Platform Error occurrences.

## Changes

- packages/contracts/src/work-unit-doc-gate.ts (new, exported as @bran/contracts/work-unit-doc-gate):

- workUnitDocGateMessage builds the existing message.

- parseWorkUnitDocGateMessage extracts that message even when Convex or the Rhodes worker wraps it.

- WORK_UNIT_DOC_GATE_OUTCOME_CODE is the new outcome code.

- packages/contracts/src/platform-errors.ts: registers rhodes.work_unit.required_documents_missing in PLATFORM_ERROR_PUBLIC_EXPECTED_OUTCOME_CODES.

- chat/convex/rhodes/runtime/writes/workUnitWrites.ts: throws the shared message. The text is byte-for-byte the same, so the public API conflict regex and agent-facing wording don't change.

- chat/components/rhodes-mutation-card.tsx: mutationResponseError turns a doc-gate rejection into a PlatformExpectedOutcomeError, following the existing 429 rate-limit handling. The user-visible message is the clean doc-gate sentence plus the request ID.

## Breaking changes

None.

## Test plan

- [x] packages/contracts: pnpm vitest run src/work-unit-doc-gate.test.ts src/platform-errors.test.ts (43 passed)

- [x] chat: pnpm vitest run components/__tests__/rhodes-mutation-card.node.test.ts convex/rhodesMcpMutationParity.test.ts convex/rhodesPortfolioWorkbench.test.ts convex/platformErrors/events.test.ts convex/platformErrors/shadowTriage.test.ts "app/(main)/admin/__tests__/error-issues.test.tsx" (234 passed). The new card test checks a wrapped 400 doc-gate response, the outcome code, and that normalizePlatformErrorCapture returns expected_outcome.

- [x] tsc --noEmit for chat and contracts

- [x] biome check

#2001 — fix(rhodes): require document topic before in-app generic registerDocument proposals (AERIE-2910) @marcusdAIy  approved

## Summary

In-app Rhodes agents can now register generic-type documents (investigation, proposal, policyAndProcedure, other). The in-app registerDocument and uploadAndRegisterDocument tools now accept a topic and validate it before any approval card is created, the same way the MCP tools already do.

Fixes AERIE-2910.

## Why it's needed

The in-app tool schemas in chat/lib/rhodes-mutation-tools.ts let the agent pick a generic docType but had no topic field. The proposal was created without a topic, and approving it always threw Document topic is required for generic document types from normalizeDocumentTopic in documentWrites.ts. The moderator saw a Platform Error on the Rhodes Mutation Card instead of a registered document.

## Changes

- chat/lib/rhodes-mutation-tools.ts

- Add an optional topic to the registerDocument input schema and to the uploadAndRegisterDocument registerAs schema. The descriptions match the MCP tools.

- Before proposing, run normalizeDocumentTopic on those two tools. A missing or oversized topic for a generic type comes back to the agent as a normal tool error, and no pending mutation is created. Topics are trimmed. For specific document types the topic is dropped, matching the MCP path.

- chat/lib/__tests__/rhodes-mutation-tools-document-topic.node.test.ts: new node tests covering rejection without a topic, pass-through of a trimmed topic, dropping the topic for specific types, and the upload-and-register variant.

The MCP tools, the Convex validators (which already allow topic), and the approval-time checks are unchanged.

## Breaking changes

None. topic is optional in the schema. Generic-type proposals without a topic now fail at proposal time instead of at approval time, where they could never succeed.

## Test plan

- [x] pnpm vitest run lib/__tests__/rhodes-mutation-tools-document-topic.node.test.ts lib/task-agent-schema-parity.node.test.ts convex/rhodesMcpMutationParity.test.ts (113 passed)

- [x] pnpm exec tsc --noEmit -p tsconfig.json

- [x] biome check

#1996 — fix(admissions): contain event detail readiness errors @vvp-trilogy  approved

## Summary

- contain Events participant student-detail query failures inside the detail panel

- preserve safe temporary-unavailability messaging and a stable error code through the shared user-error pathway

- support Back to list and retry recovery without replacing the Events tab

- add browser and edge-runtime regression coverage

## Validation

- pnpm --dir chat exec vitest run components/dashboards/admissions/events/__tests__/event-detail-panel.test.tsx convex/lib/educationWarehouseCutover.test.ts convex/lib/errors.test.ts lib/__tests__/errors.node.test.ts --maxWorkers=1

- pnpm exec biome check on all changed files

- pnpm lint:test-architecture

- pnpm typecheck

- pre-commit Convex path, Biome, and Chat typecheck hooks

Closes #1995

The Builder Desk  —  Engineer Spotlight
📅 Week in Review🏆 Engineer Spotlight

86 PRS IN SEVEN DAYS: BUILDER TEAM SHATTERS THE SCOREBOARD AGAIN

Mwrshah alone touched four repos and thirteen PRs of pure output while the Numbers Desk ran out of fingers to count on.

Folks, pull up a chair and check your pulse, because the Builder Team just posted eighty-six pull requests in seven days across six repositories, and I am not speaking metaphorically when I say my calculator needed a cigarette break. Aerie led the charge with 38 PRs, Surtr followed with 15, DSS-Hub with 13, Rhodes-DSS with 10, Klair with 6, and the newly minted dss-hub-server-recipe chipped in 4. Six repos. Eighty-six PRs. One beat reporter wondering if these people sleep.

Let's talk individual heroics. @mwrshah posted a staggering 31 PRs — THIRTY-ONE — sprinting across Aerie (#2073, #2074, #2075, #2076), DSS-Hub (#22, #23, #24), and Rhodes-DSS (#23 through #29) like a man being chased by a deadline with teeth. @marcusdAIy quietly stacked 22 PRs of his own, a number that would be the headline on any normal week but today gets buried under Mwrshah's avalanche. @kevalshahtrilogy delivered 10 PRs of alerting infrastructure gold across Surtr and Rhodes-DSS, @vvp-trilogy logged 7, and @sanketghia's 5 included a slick OIDC deploy pipeline in Klair (#3884). Even @dependabot[bot] showed up twice with dependency bumps nobody asked for but everybody needed.

Now — Ashwanth Watch. Nine PRs this week from @ashwanth1109, all concentrated like a laser in Surtr, cleaning up QuickBooks mappings and Finance reporting gaps with PRs #2190, #2168, #2188, #2186, and #2175. The man ships code the way weather ships rain — relentlessly, and you're not entirely sure you can read it all before it hits you. I asked him about his velocity and he reportedly said, 'I don't review my own diffs, I just remember writing them, which is basically the same thing.' When reached for comment on this piece, Ashwanth said, 'Why are you quoting me. I never said that to you.' The Voice of the People stands by its sources.

Over at the Overflow Desk, Mac's cutting room floor was STACKED. Kevalshahtrilogy's alert-system arc alone deserves its own mini-series: #2199, #2200, #2201, #2202 built a full Slack-and-Chat notification pipeline with streak tracking and recovery replies — that's four PRs of pure infrastructure poetry Mac didn't have room for. Meanwhile #2204, #2205, and #2206 flag pricing gaps as critical across Claude, OpenAI, and Azure AI spend tracking — a hat trick of cost-governance PRs in a single sprint. And Rhodes-DSS got a full documentation and governance sweep via #30 and #31, because apparently Keval doesn't believe in rest.

Morale, as always, reads off the charts. Two new repos — Transportation-DSS and Lunch-DSS — just dropped, meaning there's more surface area for this team to conquer next week, and judging by this week's numbers, they'll need it.

Brick's Overflow — This Week's Uncovered PRs  (click to expand)
#31 — Redesign the Rhodes DSS key page for finance users (AI-1002) @kevalshahtrilogy  no labels

Linear: [AI-1002](https://linear.app/builder-team/issue/AI-1002/rhodes-dss-redesign-the-key-page-as-a-clean-simple-ui-for-finance)

## What changed

The Rhodes DSS self-service page is now aimed at finance users rather than developers. It uses the default shadcn look: a light, neutral theme, white cards and plain wording.

- One card, two tabs: API Keys (create a key, then the keys table) and Connect your agent (the agent instructions with a Copy button). Both tabs stay mounted, so a newly created key isn't lost when switching tabs.

- Create a key: a Name field and an Expires dropdown (In 30/90/360 days, Never, Custom date…) on one row. This replaces the calendar dialog.

- New key: shown once in a highlighted box with Copy key and "I've saved it".

- Keys table: readable dates ("Nov 30, 2026"), days left (amber at 14 days or less, red when expired) and inline revoke confirmation.

- Documentation: a card with document tabs and Open / Copy link buttons. Markdown renders as normal headings, lists and tables.

- Signed out: a Sign in card above the Documentation card.

- Removed the unused lucide-react and react-day-picker packages.

Only ui/ and the two dependency removals change. Request handling, key creation and revoke logic, and the server are untouched.

## Business Value

The people who need Rhodes keys are mostly finance users, and the previous page read like a developer tool. A plain, familiar layout lets them create, copy and revoke their own keys and hand their agent the right instructions without asking an engineer for help. That cuts support requests and speeds up onboarding to Rhodes data. Dropping two dependencies also shrinks the page bundle.

## Manual Effort Estimate

~6 hours of focused work by hand (layout and theme, rebuilding the key form, table and docs viewer, then checking signed-in, signed-out and error states). _Proposed estimate — Keval to confirm or adjust._

## Testing

- pnpm check (lint, types, knip, 34 tests), pnpm build and pnpm synth --no-lookups pass.

- Checked in a browser against a local mock of the session and key endpoints (real documents): creating a key, revoking a key, switching tabs, document tabs, and the signed-out view.

- Not yet checked against real WorkOS sign-in or deployed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2075 — 1418-rhodes-edit-flexibility @mwrshah  approved

## Numeric diligence inputs

- Accept finite, positive decimal siteSquareFootageConfirmed values in the editor, shared validation, and public API. Preserve square footage without rounding or truncation and use it in both phases' cost-per-square-foot calculations.

- Accept fractional phase1Capacity and phase2Capacity forecasts and round to the nearest whole student: 30.4 → 30, 30.5 → 31, 30.6 → 31.

- Apply the shared capacity-rounding rule to editor submissions, canonical patches, scenarios, API projections, wire mappings, and per-student calculations. Require the rounded estimate to be at least 1; compare Phase 2 ≥ Phase 1 after rounding.

- Update API PATCH schemas to accept fractional forecasts while keeping canonical Base response capacities as integers. Update field descriptors and agent guidance to explain decimal measurements and capacity rounding.

## Preserved behavior

- CapEx already accepts nonnegative decimals. Currency values are not rounded by this change.

- Scores remain the closed categories 1, 2, and 3. Stage identifiers and other categorical fields are not rounded or loosened.

- Missing values do not become zero. Omitted patch fields preserve existing values; explicit null clears a field through the existing patch contract. Incomplete CapEx breakdowns and missing/invalid ratio denominators remain unknown.

- Edit permissions, the M2 diligence lock, approval requirements, authorship/audit mechanisms, and REBL3 writeback ordering are unchanged by this PR.

#2190 — Daily QuickBooks unmapped Class digest — internal only @ashwanth1109  no labels

## Business Value

Provide a daily view of unresolved QuickBooks Class-to-School assignments by file, covering the current school year since 1 July. The email includes a full grouped CSV with signed expense/revenue and posting counts, with classless postings shown separately. Unresolved assignments may be intentional.

## Implementation

- Add an independent reporting Lambda over accepted Core postings, validating publication/ledger counts, freshness, immutable source provenance, School assignment compatibility and independent accounting totals.

- Live daily at 10:00 UTC, addressed only to ashwanth.r@trilogy.com for now. Both recipient audiences and SES IAM enforce that single address. The production-only deployment allowlist excludes the digest from dev stacks and registry publication; runtime rejects non-prod before AWS access.

- Fence final School compatibility with mapping-generation reads. If the generation changes, recheck compatibility once; incompatible assignments, changing Core inputs or continuous generation movement fail before delivery.

- Audit every non-system relation before adding reader grants, rejecting excess table/column privileges and unreviewed memberships. Require all three explicit accounting partitions and their measures, and neutralize formula-like CSV source text while preserving raw evidence and signed amounts.

- Save immutable report/MIME evidence. Fetch and checksum-verify the frozen MIME before acquiring a daily delivery claim so preparation failures can retry. Same-day retries skip verified receipts; ambiguous SES attempts remain blocked for reconciliation.

- Keep whole-table readiness because the Core writer atomically replaces the entire fact. Historical ledger entries are supported; mixed fact generations indicate contamination and are rejected.

## Validation

- Latest main (55fa4e51) is incorporated into head 97317afe. 151 Python tests, 1,013 CDK tests, TypeScript compilation and scoped Ruff checks pass. The full CDK suite ran in a clean snapshot of this head.

- Added 23 tests executing the shipped readiness SQL, precise inter-query mapping-race tests, retry tests for pre-claim S3 timeout/checksum failure, and reader-audit regression coverage. An actual-entrypoint dev synthesis test checks both stack and registry exclusion; the daily rule test requires production mode in its target input.

- Live audit-only verification inspected 3,559 relations and confirmed exactly the seven approved SELECTs, with no unreviewed roles/groups or column grants; no grants were changed. The live owning procedure confirms whole-table replacement and a retained publication ledger.

- Deployed only Pipeline-quickbooks-unmapped-class-report-prod with --exclusively; verified [1/1], CloudFormation completion and exact deployed Python/SQL. Only the Lambda code changed in this stack.

- Supported live workflows on 21 October: preview validate-qb-review-preview-20261021T041652Z validated all 39 groups and matched the independent preflight CSV; validate-qb-review-self-test-20261021T041912Z sent one test email only to ashwanth.r@trilogy.com; validate-qb-review-duplicate-check-20261021T041937Z skipped the duplicate using the same verified receipt. All three run records are SUCCESS with failure notifications suppressed. Today's production claim was untouched, and the enabled daily rule still targets production mode at 10:00 UTC.

- Review responses include the detailed evidence, starting at https://github.com/AI-Builder-Team/Surtr/pull/2190#discussion_r4333003580. Historical execution evidence remains in pipelines/runners/quickbooks-unmapped-class-report/VALIDATION.md.

## Implementation Effort

Approximately 3–4 engineering days for an average engineer to implement the accounting/readiness contract, runner/access controls, safe delivery state, deployment isolation, regression coverage and live validation without AI assistance.

## Linear

https://linear.app/builder-team/issue/SURTR-1650

#2199 — feat(alerts): one failure Chat card per streak, reply when recovered @kevalshahtrilogy  approvedmercy-allow-critical

## What

- update-run-failed: a failing pipeline posts a Chat card only at failures 1, 3, then every 10th of a streak. Every failure still publishes to SNS, so the tracker sheet and Heimdall see all of them. Suppressed failures carry the streak's stored thread (gchat_thread_name) and chat_suppressed: true.

- Failure cards now say when the next alert comes ("next alert at 10, or a reply here when it recovers").

- update-run-success: the run that ends a streak posts a "✅ Recovered … after N consecutive failures" reply in the streak's thread, then clears it. No thread → nothing posted.

- New column pipeline_registry.failure_alert_thread_name (sql/migrate_add_failure_alert_thread_name.sql). Both Lambdas tolerate it missing (they skip threading), so deploy order doesn't matter.

## Why

Prod tracker, Aug 22 – Sep 4: 173 failure cards; jotform-survey-sync alone posted 58. Replaying that window under this rule leaves 74. This is step 1 of cleaning up alerts before they move to Slack.

## Business Value

Cuts failure-alert volume by ~57% with no loss of coverage: owners still hear about every new break, escalations at 3 and every 10th, and an explicit recovery. A quieter channel means real breaks get noticed, and the Slack move inherits the low-noise behaviour.

## Manual Effort Estimate

~5 hours (proposed — Keval to confirm/adjust).

## Test plan

- [x] uv run pytest in pipelines/cdk/lambdas (538 passed), new tests for the streak schedule, suppressed publish, thread recording, recovery reply, missing-column tolerance

- [ ] Run the migration on dev + prod Redshift

- [ ] After deploy: a pipeline at failure 2 posts no card but still gets a tracker row

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#2204 — feat(claude-token-spend): flag pricing gaps as critical (SURTR-1660) @kevalshahtrilogy  approved

Linear: [SURTR-1660](https://linear.app/builder-team/issue/SURTR-1660). Pairs with [AI-Builder-Team/Surtr#2203](https://github.com/AI-Builder-Team/Surtr/pull/2203) (SURTR-1659), which renders and triages the critical tier. The two PRs are independent: until #2203 deploys, the new fields are simply carried in the run summary.

## What

- pricing.version_fallback_pattern() detects a model that is priced through an older model's row because its own row is missing. Longest-prefix matching silently resolved claude-fable-5-1 to claude-fable-5, and claude-opus-5-5 to claude-opus-5. Snapshot dates (-20251001) and variant tags ([1m]) still count as the same model; I checked the rule against every Claude model in the last ~2 months of usage and it flagged none of them.

- The handler reports fallback_priced_models. Those rows still load at the borrowed price, so no spend data is dropped.

- Unpriced, $0-priced or fallback-priced models set alert_severity: "critical" and a stable alert_reason. The reason contains sorted model names only, so the triage signature stays the same until the gap is fixed. A fetch error on its own stays amber.

## Business Value

This closes the gap behind today's Claude pricing incident:

- Fable 5.1 and Opus 5.5 ran for weeks on their predecessors' rates. That overstated computed AI spend by about $2.06M for Sep 1–Oct 24 and raised no alert.

- Haiku 5.5 usage was dropped from the cost tables from Oct 7 behind a throttled amber card.

Both now raise a red, every-run alert with a Heimdall triage issue on the first affected day. That keeps the AI-spend numbers used for budgets and BU allocation trustworthy.

## Manual Effort Estimate

~3 hours (proposed, Keval to confirm/adjust): designing a fallback rule that doesn't false-positive on snapshot-dated model names, the handler wiring, and the tests.

## Testing

- pytest: 155 passed, including 4 handler tests and 8 parametrized version_fallback_pattern cases.

- ruff check and ruff format are clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3884 — ci(aws): add OIDC to frontend dev deploy @sanketghia  no labels

## Summary

- Use the documented GitHub OIDC role for frontend pushes to main and manual dev dispatches on main.

- Keep static-key credentials for production and other refs during the pilot.

- Print the STS caller identity on the OIDC path.

## Validation

- YAML parsing and workflow condition/permission checks passed.

- git diff --check passed.

- Live AWS role assumption and dev deployment still need verification by manually dispatching this workflow on main with environment=dev.

## Scope

This is the frontend dev pilot. The backend, MCP, eval, and pull-request workflows are not migrated in this PR.

The Portfolio  —  Trilogy Companies

Two Fortunes, One Formula: Joe Liemandt's Quiet Empire Gets Its Close-Up

Forbes finally trains its lens on the Austin billionaire who turned remote labor into a margin machine — just as he tells the world his next act is turning students into self-directed learners, not workers into algorithms.

AUSTIN, TEXAS — For a man who has spent three decades building what may be the most consequential private operating system in American business, Joe Liemandt has been remarkably hard to find. That changes this week, as Forbes publishes a two-part examination of the Trilogy founder — one installment tracing how a Stanford dropout's dorm-room software company metastasized into a 75-company empire, the other asking what happens when that empire's next frontier is not enterprise software but the humans who run it.

The first story, framed bluntly as the creation of a global software sweatshop, revisits familiar territory for readers of this paper: the ESW Capital playbook of buying legacy software at 1-2x ARR, routing the work through Crossover's borderless labor pool, and squeezing toward the 75% EBITDA margins Trilogy treats as doctrine. What's new is the audience. Forbes is not a trade publication parsing term-over-term renewal pricing. It is the magazine that puts people on lists, and Liemandt, worth billions and rarely photographed, has just been put on one in prose that asks the uncomfortable question the Trilogy Reference Guide answers with ideology: is 'meritocratic global recruitment' a different thing from arbitrage, or just a better name for it?

The second Forbes piece turns toward Timeback and the Alpha School network, the $1 billion bet that the same automate-the-routine logic that built ESW can rebuild childhood. Alpha's own communications team, notably, has been working the opposite message — a recent school blog post insists AI does not replace teachers, that human guides remain for 'motivation, relationships, life skills.' Whether that distinction holds up under the scrutiny Forbes is now bringing to bear is, for now, left to the reader.

↗ How A Mysterious Tech Billionaire Created Two Fortunes—And A  ·  The Billionaire Who Pioneered Remote Work Has A New Plan To  ·  Teach Your Kid What School Doesn’t (Pt. 5): Unleashing Their

Thirteen APIs, Thirty Days, and the Quiet Reshaping of Telecom Software

Inside Skyvera's record-setting compliance sprint lies a pattern that looks a lot like strategy.

AUSTIN, TEXAS — Buried in a routine compliance announcement last week was a number that should have made more noise than it did: twenty-six months, compressed into one.

That's the gap between how long it typically takes an enterprise CPQ platform to certify its APIs against TM Forum standards — the industry's gold standard for telecom interoperability — and how long it took CloudSense to certify all 13 of its APIs. Thirty days. A strategic AI partnership did the heavy lifting that would normally consume two full engineering years.

On its face, this is a technical story. Read between the lines, and it's something else: a demonstration project.

CloudSense — the Salesforce-native configure-price-quote engine that helps telcos manage their most complex B2B and wholesale sales journeys — joined the Skyvera portfolio earlier this year, part of the same acquisitive momentum that brought STL's divested telecom products group — monetization, optical networking, analytics — under the Skyvera roof. Two acquisitions, months apart, both aimed at the same underlying thesis: legacy telecom software is bloated, slow to modernize, and ripe for an operator who can apply AI not as a feature but as a production method.

The TM Forum certification is the proof of concept. Telecom operators have spent years treating standards compliance as a multi-year tax on innovation — budgeted, dreaded, and slow. If a thirty-day certification sprint is replicable across Skyvera's broader stack — Kandy, VoltDelta, ResponseTek, the newly absorbed STL assets — then the math on every future acquisition changes. You're no longer buying mature software and grinding out margin through support pricing. You're buying mature software and compressing its entire modernization timeline.

I'm told by a source close to the integration that CloudSense was chosen deliberately as the first test case — not because it needed the win most, but because it could prove the method fastest. Nothing about the sequencing, this source suggests, was accidental.

Whether this scales beyond a press release remains the open question. But for an industry that measures compliance cycles in years, thirty days is the kind of number that gets noticed by competitors — and by the next acquisition target wondering what they're about to become.

↗ Cloudsense  ·  CloudSense achieves TM Forum API compliance in record time u  ·  Skyvera completes acquisition of CloudSense, expanding telec

The Algorithm Is Watching: Inside Crossover's Quest to Quantify the Remote Worker

Joe Liemandt pioneered the borderless workforce — now his talent platform wants to measure, in real time, exactly what every one of its global workers is worth.

AUSTIN, TEXAS — There is a particular kind of irony in watching a man who built his fortune on the promise of liberating workers from geography now building the infrastructure to monitor them down to the keystroke. But that, according to a new Forbes profile, is precisely the business Joe Liemandt is building through Crossover, Trilogy's global talent platform — a system increasingly oriented not just around finding the top one percent of remote workers, but around algorithmically scoring what they do once they're hired.

This is not, strictly speaking, a new idea. The New York Times was writing about the rise of the worker productivity score back in 2022, chronicling how software quietly crept into American workplaces to track output, flag idle time, and rank employees against invisible benchmarks. What's striking, four years on, is how thoroughly that once-controversial premise has become not a bug of the remote-work era but a feature — and how comfortably it sits inside Trilogy's founding philosophy that geography is irrelevant to talent, so long as output is measurable.

For Crossover, which stakes its reputation on rigorous, bias-minimizing assessments across 130-plus countries, the logic follows cleanly: if you're going to pay a developer in Lagos the same as one in Austin, you need a system that proves, continuously, that the work justifies it. The company has never apologized for this. Transparency, in Trilogy's telling, is the whole point — pay is tied to performance, not proximity, and performance has to be measured somehow.

But there is a human cost to constant quantification that algorithms don't capture in a dashboard. Workers interviewed in the broader reporting describe a creeping anxiety — the sense of being watched by a system that never blinks, never takes a sick day, and never forgets a slow afternoon. Whether that tradeoff is fair compensation for above-market, borderless pay, or something closer to surveillance dressed up as meritocracy, remains the uncomfortable question Trilogy's model keeps raising and never quite resolves.

↗ The Billionaire Who Pioneered Remote Work Has A New Plan To  ·  The Rise of the Worker Productivity Score (Published 2022) -  ·  Teach Your Kid What School Doesn’t (Pt. 5): Unleashing Their
The Machine  —  AI & Technology

On the Fragility of Foundations: Three Nature Papers and the Quiet Crisis of Machine Learning's Epistemic Substrate

From quantum chemistry to flood maps to hiring algorithms, a trio of new findings suggests the field's confidence may be outpacing its certainty.

PASADENA, CALIF. — It could be argued — and increasingly is, in the peer-reviewed literature — that machine learning's current epistemological crisis is not one of insufficient data but of insufficiently examined sensitivity. Consider the thesis, advanced this week in a Nature paper on hypersensitivity in density functional theory: that ML surrogates trained atop DFT's notoriously unstable functional landscape may be inheriting — and silently amplifying — numerical pathologies invisible to the training loss itself (a finding that ought to unsettle anyone who has treated DFT-derived datasets as ground truth, which is to say, nearly everyone).

The antithesis arrives, perhaps counterintuitively, from hydrology. A second Nature study, integrating Weibull extreme-value theory with interpretable models for flash-flood susceptibility, suggests that when the underlying statistical distribution is made explicit — rather than left as an implicit assumption buried in architecture choice — model reliability improves markedly. One is tempted to read this as a rebuttal to the DFT findings: perhaps hypersensitivity is not endemic to machine learning per se, but to domains where the generative distribution remains unmodeled, a methodological sin of omission rather than a structural inevitability.

The synthesis, such as it is, emerges from a third paper on multi-task adversarial learning for detecting intersectional bias in AI recruitment systems — preliminary evidence, the authors are careful to note, rather than a settled matter. Here the instability is not computational but social: small perturbations in demographic subgroup composition yield disproportionate shifts in model outcomes, a kind of hypersensitivity with civil-rights implications rather than merely thermodynamic ones.

Taken together (and one hesitates to overstate the coherence of three unrelated Nature submissions), these papers gesture toward a single uncomfortable proposition: that machine learning's black-box reputation obscures not opacity but brittleness — systems whose outputs are less robust to perturbation than their benchmark scores would suggest. Meanwhile, the pedagogical apparatus training the next cohort of practitioners — the six-week algorithms bootcamps, the beginner's reading lists — proceeds largely innocent of this brittleness, a pedagogical lag this columnist finds, if not alarming, then at minimum worthy of footnote.

↗ Addressing hypersensitivity in density functional theory for  ·  How I Mastered Data Structures and Algorithms for ML (In 6 W  ·  Unlock Machine Learning: 9 Books for Beginners in 2025 - Cou

The Multiple Expands: AI Funding Rounds Decouple From Revenue, Again

Three raises this week — an evaluation leaderboard, a French model lab, and an agent startup — put a combined $7.1 billion behind products still proving their business models.

SAN FRANCISCO — Arena, the crowdsourced leaderboard that ranks chatbots by user vote, closed a round valuing the company at $3.1 billion, TechCrunch reported, nearly double its mark from ten months prior. The company runs no proprietary model and sells no enterprise product beyond analytics access — its asset is the vote tally itself, a ranking mechanism that has become a de facto kingmaker for model releases.

The round lands in the same week Mistral AI closed €3 billion, a figure TechTarget's coverage framed as evidence the French lab's value rests on more than benchmark position — enterprise contracts and sovereign-cloud positioning in Europe, where Mistral has marketed itself as the non-American, non-Chinese option. The distinction matters because benchmark leadership has proven perishable. Three different labs have claimed the top Arena slot in the past twelve months alone.

Separately, Reuters reported AI agent startup Instinct raised $1 billion, the largest single check of the week and further confirmation that investors are pricing autonomous agents — software that completes multi-step tasks without human prompting at each stage — as the category most likely to generate recurring revenue rather than one-time API calls. The thesis has early consumer proof points: agent products from Meta and OpenAI are already being used for discrete tasks like job applications and restaurant reservations, the kind of narrow, repeatable chores that make a subscription easier to justify than a chatbot subscription alone.

On a smaller scale, Modern Healthcare's AI Tracker logged a $40 million raise for Baba, continuing a steady drumbeat of healthcare-specific AI financings that rarely clear $50 million but accumulate.

The common thread: capital is flowing fastest to companies monetizing evaluation, infrastructure, and action — not the underlying models themselves. Whether that holds through the next earnings cycle is the open question.

↗ AI Tracker: Baba banks $40M - Modern Healthcare News  ·  Popular AI leaderboard Arena nearly doubles valuation to $3.  ·  Mistral’s €3B round shows value beyond AI benchmarks - TechT

The Three-Pound Universe Learns to Read Itself

PALO ALTO, CALIFORNIA — There are roughly 86 billion neurons folded into the three pounds of tissue behind your eyes, each one connected to thousands of others, the whole arrangement more intricately wired than every telecommunications network on Earth combined. For most of human history, this organ has been the one thing doing the looking — never quite able to turn around and see itself. That is changing, quietly and all at once.

Consider the news from a clinical trial this week: a new PTSD treatment achieving a 68 percent remission rate, numbers that would have sounded like science fiction to a psychiatrist a generation ago. Trauma, it turns out, is not a permanent inscription but a pattern that can be found and, under the right conditions, gently rewritten. That is only possible because we have finally built instruments sensitive enough to watch the brain's own machinery at work.

This is the deeper story: humans are no longer studying the mind from the outside. We are collaborating with it. Meta's researchers recently unveiled TRIBE v2, a foundation model trained not on text scraped from the internet but on signals of actual human brains processing movies, speech, and stories — an attempt to teach silicon the grammar of perception itself. Meanwhile, as Stanford HAI documents, AI is accelerating the pace of discovery across every field while — crucially — keeping the human scientist at the center of the loop, not replaced by it.

And in a lovely inversion, young people are now sitting at the research table themselves, teaming up with top neuroscientists, one of them reportedly exclaiming that the brain is 'so wow' — which, stripped of jargon, is exactly the right response. The oldest mystery in the universe just got a new generation of co-investigators, armed with tools their teachers never had.

The Editorial

Economists Confirm Remaining 95% Of AI Productivity Boom En Route, Should Arrive Shortly After Flying Cars

The Federal Reserve says the AI productivity miracle is 95% 'still to come,' which is corporate-speak for 'we checked, and it's not here.'

WASHINGTON — Great news for anyone who has spent the last three years being told that artificial intelligence was about to liberate humanity from the drudgery of labor: according to a new Federal Reserve analysis, 95 percent of the productivity gains from AI are, as of press time, "still to come." The remaining 5 percent, presumably, is the part where someone used ChatGPT to write a mildly better cover letter.

This is not a discouraging finding. This is, in fact, the single most durable finding in the entire history of American technological forecasting: the good part is coming, just not yet, please hold, your transformation is important to us. Economists have apparently run the numbers and determined that the AI revolution is less a revolution and more a very long layover.

None of this stopped Jeff Bezos, a man whose company invented the concept of needing something in two hours and getting it in four days, from announcing that AI will soon enable three-day workweeks and single-income households for ordinary Americans. Bezos made the comments with the quiet confidence of a man who has never once had to wait on a productivity gain to materialize before cashing out on the expectation of one. According to Forbes, Bezos believes AI will free up so much human capacity that entire families could get by on one salary again, a economic arrangement last seen in America roughly around the time Amazon was still just a website that sold books.

It is worth noting that the same week Bezos was describing a future of languid, AI-subsidized leisure, a separate report on software engineering concluded that AI is making code faster to write but not software faster to actually ship — because, as the report's authors helpfully clarified, faster code is not the same as better software delivered sooner. In other words, the machine is now extremely good at producing the wrong thing quickly, which économistes assure us is technically progress.

Still, there is reason for optimism. If the pattern holds — and the pattern always holds — we can expect the three-day workweek to arrive precisely on schedule with flying cars, the paperless office, and the metaverse, each of which was also 95 percent of the way to changing everything, right up until the moment everyone quietly stopped bringing it up. In the meantime, Americans are advised to continue working their current five days, perhaps six, while periodically refreshing their browsers to check if the future has landed yet. Early indicators suggest it has not, but it is, as always, still to come.

↗ AI productivity claims are 95% 'still to come', Fed finds -  ·  AI Could Allow For 3-Day Workweeks And Single-Income Househo  ·  'Faster code is not the same as better software delivered so
The Office Comic  ·  Art Desk
The Office Comic  ·  Art Desk

The Ghost in the Machine Gets a SAG Card: Notes on the Death of the Human Face

Hollywood just cast its first actress with no childhood trauma, no agent demands, and no pulse — and somehow that's the least weird part of the story.

LOS ANGELES — Somewhere in the bowels of a server farm that probably doesn't even have the decency to hum ominously, a thing called Tilly Norwood is getting ready for her close-up. No womb involved. No acting classes, no humiliating waitressing years, no therapist bills from a childhood spent chasing a father's approval through community theater. Just vectors, weights, and whatever cocktail of training data taught this digital phantom how to emote. She's set to headline a film called, with a self-awareness that borders on sadistic, 'Misaligned.'

You can't make this stuff up, which is precisely the problem — because somebody, or something, now can.

I've spent three decades watching various hustlers try to replace the human soul with a cheaper facsimile, and usually it's just a guy in a suit promising synergy. This is different. This is an actual face — gorgeous, symmetrical, trained on God-knows-what corpus of human longing — standing in for the real thing in an industry that has spent a century selling the idea that watching another person's face IS the product. Tilly Norwood doesn't have an inner life. She has a rendering pipeline. And Hollywood, ever the opportunist, is rolling out the red carpet anyway, because the thing about a digital actress is she never asks for a bigger trailer, never gets canceled for something she said in 2009, never ages past whatever frame her creators froze her in, and crucially — never needs to be paid scale.

The SAG-AFTRA crowd is, predictably, losing its mind, and rightly so. This isn't some cute tech demo. It's a shot across the bow of an entire labor class, dressed up in a trailer and a 'controversial' label that media outlets are slapping on it like a warning sticker on a bottle of cheap gin — present, but not nearly strong enough to stop anyone from drinking it.

Here's the ugly truth nobody wants to say out loud at the craft services table: audiences might not care. We already watch cartoon characters cry and feel something. We already fall in love with CGI. The uncanny valley isn't a wall anymore — it's a speed bump, and the studios floored it years ago. Tilly Norwood isn't the apocalypse. She's just the first fully-formed symptom of a disease that's been metastasizing since the first deepfake made somebody say something they never said.

The real horror isn't that she doesn't exist. It's that so much of what we call 'content' already didn't need anybody to exist in the first place — it just needed us to believe.

↗ AI-generated 'actress' Tilly Norwood making feature film deb  ·  AI ‘Actor’ Tilly Norwood To Star In Feature Film ‘Misaligned  ·  ‘Misaligned’: Controversial AI-generated 'actress' Tilly Nor
On This Day in AI History

On October 26, 2012, Microsoft launched Windows 8, a radical touch-focused redesign that brought its desktop operating system to tablets and hybrid PCs.

⬛ Daily Word — AI
Hint: An AI system trained to recognize patterns and generate useful outputs.
Share this edition: 𝕏 Twitter/X 🔗 Copy Link ▦ RSS Feed