Tyler Butler

This commit significantly **improves the first-run onboarding experience** across all **Codespaces devcontainer profiles**, with a special focus on the **AI-enabled environment**. It introduces profile-specific terminal welcome messages via `first-run-notice.txt` and **refactors devcontainer lifecycle hooks** to optimize prebuilds by moving Node.js setup to `onCreateCommand`. For the AI-enabled profile, new capabilities include an auto-opening `GETTING_STARTED.md` guide, an integrated CodeTour for guided learning, and an `ai-reset` alias for environment management. These changes provide a more guided and efficient initial setup for Codespaces users.

This commit significantly **improves** the `ci-readiness-check` skill, an **enhancement** based on systematic evaluation, by refining its underlying shell script (`ci-readiness-check.sh`) and clarifying its instructions (`SKILL.md`). The updated script now leverages `fluid-build --task checks:fix` for comprehensive **auto-fixing of formatting, policy, and version consistency issues**, includes a `pnpm install` guard, and verifies fixes post-auto-fix. This ensures **correct tool usage** (e.g., Biome over Prettier) and enables the skill to **auto-fix common CI issues** like missing API reports or changesets, achieving a **100% pass rate** in evaluations and greatly improving developer CI workflow efficiency.

This commit performs **documentation maintenance** by cleaning up the **`eslint-config-fluid`** changelog, specifically for the **9.0.0 release**. It consolidates previously unreleased changes into the 9.0.0 entry and removes outdated or duplicate sections, such as `FlatCompat` details and dependency-only notes. The update also clarifies wording regarding temporarily warned `react-hooks` rules and rule promotions, ensuring the changelog provides accurate and concise information for users. This **cleanup** improves the clarity and readability of the release notes for the `eslint-config-fluid` package.

This commit **removes a flaky test** from the **build-cli** component, specifically within the `canonicalizeChangesets.test.ts` file. The test, titled "should write all changesets in parallel", was causing intermittent CI failures due to unreliable concurrent git operations in the test environment. This **maintenance fix** addresses a **test stability issue**, preventing future false negatives and improving the overall reliability of the **CI pipeline**. By eliminating this problematic test, the project's automated checks become more consistent and trustworthy.

This commit **restores the `@fluidframework/eslint-config-fluid` package as an independent workspace**, reversing its temporary inclusion in the client release group. This **maintenance** change prepares the package for its upcoming **v9.0.0 release with ESLint 9 flat config support**, enabling independent publishing and versioning. It involves significant updates to the **build system configuration** (`pnpm-workspace.yaml`, `fluidBuild.config.cjs`), adjusts dependency resolution for **client packages** to use a new catalog group, and re-enables publishing tasks for the linting configuration.

This commit **rewrites** the `.changeset/README.md` file, transforming it into a **comprehensive, self-contained guide** for the project's changeset workflow. This **documentation improvement** consolidates information previously scattered across the wiki, now detailing the changeset format, custom metadata, release note sections, and formatting guidelines with practical examples. The change significantly enhances the clarity and accessibility of **changeset creation** for contributors, providing a single source of truth and reducing reliance on external documentation.

This commit introduces the **Nori senior-swe profile** as a significant **new capability** within the `repoverlay` library, providing a comprehensive AI agent with a wide array of specialized skills and subagents. It adds numerous **skills** covering areas like brainstorming, TDD, debugging, code review, and Git worktrees, along with **subagents** such as a codebase analyzer, pattern finder, and web researcher, all configured via `CLAUDE.md` and `nori.json` files. A **bug fix** is also included in `scripts/codespace-setup/agent-aliases.sh` to ensure model flags are passed correctly, and a new `nori` alias simplifies profile activation. This enhancement significantly expands the AI agent's functionality, enabling it to perform complex development tasks and interact more effectively with the codebase.

This commit **integrates the `hk` git hook manager** into the project's **developer tooling**, establishing a new **pre-commit hook** for automated code formatting. It configures `hk.pkl` to run `biome format --write` on staged files, ensuring consistent code style before commits and extending the `Builtins.biome` step for format-only operations. This **new capability** significantly enhances the **build process** by enforcing formatting standards. Furthermore, comprehensive **documentation** for `hk` installation and usage is added to `DEV.md`, facilitating adoption of this **developer experience improvement**.

This commit performs **maintenance** by removing **obsolete ESLint disable comments** from the **Tree DDS** codebase. Specifically, it removes `@typescript-eslint/strict-boolean-expressions` disable comments from `experimental/dds/tree/src/migration-shim/migrationShim.ts` and `import-x/order` comments from `packages/dds/tree/src/test/tableSchema.spec.ts`. This action cleans up the codebase, ensuring that linting rules are applied consistently where appropriate and reducing unnecessary code annotations. The change improves code readability and maintainability within the `tree` package by removing no-longer-needed suppressions.

This commit introduces a **new feature** by adding an initial instruction to the `copilot-oce` alias. Specifically, it enhances the **development environment setup** within `scripts/codespace-setup/agent-aliases.sh` for the `ff-oce` agent. This change aims to provide better guidance or configuration for users interacting with the `copilot-oce` alias in **devcontainer** or **codespace** environments, improving the initial experience.

This commit **enhances the devcontainer setup** by introducing an optional `INSTALL_AGENCY` build argument to install the **Agency tool**, configuring system-wide `PATH` integration for it, and employing stricter `curl` transport flags for its installation. This **new capability** allows developers to easily include Agency in their environment while improving security for the installation process. Concurrently, the **AI-agent Codespaces host CPU requirement is updated from 16 to 32 cores** in `.devcontainer/ai-agent/devcontainer.json`, ensuring sufficient resources for the AI agent development environment. This work provides a **new capability** for developers needing Agency and **maintains optimal performance** for AI-agent development.

This commit **enhances the development container environment** by adding the `bubblewrap` (`bwrap`) package to the `.devcontainer/Dockerfile`. This **maintenance update** ensures that developers working within the devcontainer have access to this sandboxing utility. The change specifically affects the **devcontainer setup**, making `bwrap` available for any development tasks that require process isolation or secure execution. This resolves a dependency issue, improving the robustness and functionality of the development environment for all users of the devcontainer.

This commit significantly enhances the **devcontainer environment** by adding optional installations for `agency` and `repoverlay` tools, alongside enabling SSH and ADO Codespaces authentication for the **AI agent devcontainer**. A major **new capability** is the introduction of the `ff-oce` overlay for `repoverlay`, which provides a specialized Claude agent and Kusto skill tailored for the **Fluid Framework Client OCE rotation**, complete with a comprehensive query reference for telemetry investigation. Additionally, it **refactors** shell alias setup for improved `bash` and `zsh` compatibility, and includes **fixes** for `nvm` sourcing in `post-create.sh` and a graceful guard for `playwright-cli` setup. These changes collectively improve developer tooling, AI assistance, and the overall robustness of the development environment.

This commit performs a **build maintenance** task by **bumping the client release group versions** from `2.91.0` to `2.92.0`. This change affects a wide array of **client packages**, including various Distributed Data Structures (DDSs), drivers, and core framework components, by updating their internal `pkgVersion` constants. It is a crucial step in **release preparation**, signaling the start of the next development cycle for version 2.92.0. This ensures all client-side components are aligned for future development and releases, following the completion of the 2.91.0 release.

This commit **prepares for the 2.91.0 minor release** by **adding the generated release notes and per-package changelogs**. It introduces the `RELEASE_NOTES/2.91.0.md` file, which comprehensively details new features and API changes for this version. This is a crucial **release preparation** task, ensuring that **documentation** for the upcoming 2.91.0 release is complete and available to users. This work is part of the standard release workflow and must be merged prior to the official version bump.

This commit performs **release preparation** for the upcoming **2.91.0 release** by **refactoring** how assertion messages are handled. It **tags untagged assert shortcodes** by replacing a literal error message in `quillFormattedView.tsx` within the **React framework** with a new numeric shortcode (`0xce2`). Concurrently, `assertionShortCodesMap.ts` in the **test runtime utilities** is updated to map this new shortcode to its corresponding error message. This standardization of assertion identification improves maintainability and consistency across the codebase.

This commit delivers a **bug fix** to the **CI/CD release dispatcher workflow** by resolving a validation error that prevented its successful execution. It replaces the disallowed `${{ github.event_name }}` expression with the pre-populated and allowed `${{ env.GH_AW_GITHUB_EVENT_NAME }}` environment variable within the prompt generation steps of `fluid-release-skill-dispatcher.lock.yml`. This change specifically addresses an `ERR_VALIDATION` during variable interpolation, ensuring the **release process** can proceed without interruption. The fix prevents failures in the "Interpolate variables and render templates" step, maintaining the stability of automated releases.

This commit **fixes a failure in the AI agent Codespace's `postCreateCommand`** by improving the robustness of its development environment setup. It **refactors the `scripts/codespace-setup/post-create.sh` script** to reliably install the correct Node.js version using `nvm`, addressing environment overrides and shell execution nuances. Furthermore, the **AI agent devcontainer configuration** (`.devcontainer/ai-agent/devcontainer.json`) is updated to ensure Playwright CLI installation and proper Node.js version overrides, supported by conditional Playwright CLI installation logic in the main `.devcontainer/Dockerfile`. This ensures a consistent and functional **AI agent development environment** within Codespaces.

This commit **refactors** the **devcontainer setup** for **AI agency installation**, transitioning it from an automatic build-time process to an **on-demand script**. The `AI_READY` build argument and direct agency installation have been removed from the Dockerfile, simplifying image builds and making them faster. Developers can now install the AI agency explicitly using `pnpm run install:agency`. This change primarily affects the **`ai-agent` devcontainer configuration** and **Codespace setup scripts**, streamlining the development environment and removing a deprecated corepack workaround from `post-create.sh`.

This commit introduces a **new CI/CD capability** by adding the **`fluid-release` skill** and its corresponding **`fluid-release-skill-dispatcher` workflow**. It includes comprehensive documentation for the `fluid-release` skill, detailing its interactive/autonomous modes, release process steps, and operational guidelines. Supporting reference documents outline minor release preparation, execution, the 2.x release schedule, and type test updates. The `fluid-release-skill-dispatcher` workflow, also documented, will orchestrate the execution of this new skill. This addition aims to streamline and automate aspects of the **Fluid Framework release process**.