Promote IFluidDevtools to beta

[jikim-msft]

Description

This PR promotes IFluidDevtools interface from alpha to beta for integration into partner repos.

[Copilot]

Pull Request Overview

This PR promotes the IFluidDevtools interface and related components from alpha to beta stability level to support devtools integration in Office-Bohemia.

• Updated API stability tags from @alpha to @beta for devtools interfaces
• Added IFluidDevtools interface to the beta API surface
• Updated alpha API report to reflect the promotion

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/tools/devtools/devtools-core/src/IFluidDevtools.ts	Changed JSDoc tag from @alpha to @beta
packages/tools/devtools/devtools-core/src/ContainerRuntimeDevtools.ts	Changed JSDoc tag from @alpha to @beta for ContainerRuntimeProps
packages/tools/devtools/devtools-core/src/ContainerDevtools.ts	Changed JSDoc tag from @alpha to @beta for ContainerDevtoolsProps
packages/tools/devtools/devtools-core/api-report/devtools-core.beta.api.md	Added IFluidDevtools interface to beta API surface
packages/tools/devtools/devtools-core/api-report/devtools-core.alpha.api.md	Updated IFluidDevtools tag from @alpha to @beta

[alexvy86]

We need to also make initializeDevtools and/or tryGetFluidDevtools beta, right? Exposing just the interfaces doesn't really let applications do much, since they are not designed to be implemented externally.

[Josmithr]

Have you verified that devtools-core's package.json includes an export for the beta level? If not, these APIs still won't be importable via /beta. I can help you make the necessary changes if not / you have questions :)

[jikim-msft]

Thanks for pointing out! Didn't know adding beta field in package.json is necessary.

I've referenced pacakges/dds/tree and added new esm & cjs config files and the new fields in the package.json.

[alexvy86]

Left a few more comments. I also think API report regeneration is needed? Some of the changes in the ts files aren't reflected in the API reports (readonly on some properties).

[github-actions]

🔗 Found some broken links! 💔

Run a link check locally to find them. See
https://github.com/microsoft/FluidFramework/wiki/Checking-for-broken-links-in-the-documentation for more information.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

 ELIFECYCLE  Command failed with exit code 1.

[alexvy86]

Looks good to me :)