Document astro dev --no-lock flag

[matthewp]

Documents the new astro dev --no-lock flag added in withastro/astro#17331.

• Adds a --no-lock reference section under astro dev
• Lists --no-lock in the astro dev help output

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/reference/cli-reference.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[github-actions]

Preview deployment

✅ Deployment complete!

• Latest commit: 0c3f83c
• Preview: https://dev-no-lock-flag-docs.previews.docs.astro.build
• Workflow run: View logs

[yanthomasdev]

LGTM

[ArmandPhilippot]

Mostly a nit regarding formatting (single/two paragraphs as the two statements do not seem to be linked), but I also think it's important to mention what happens when these flags are combined (see my suggestion). Otherwise, LGTM!

[ArmandPhilippot]

Reading that, I wondered what happens when these flags are combined: does one takes precedence? do I get an error? Looking at the JSDoc, it seems this throws an error. I think it's important to mention it.

Also, I think the parentheses can be shortened.

But, I'm not sure how to combine both in a logical way. I mean the two statements are not tied so I'm not sure a single paragraph makes sense... and maybe two independent paragraphs are easier to scan?

Suggested change

	The new server is not tracked by `astro dev stop`, `astro dev status`, or `astro dev logs`. `--no-lock` cannot be combined with `--background` (including when background mode is triggered automatically for an AI coding agent) or `--force`, since both rely on the lock file.
	The new server is not tracked by `astro dev stop`, `astro dev status`, or `astro dev logs`.
	When combined with `--background` (including when triggered by an AI coding agent) or `--force`, an error is throwned, as both rely on the lock file.