Opening a dynamic route renames the file and strips Astro's route syntax

Environment

What happens

Opening an Astro dynamic route in Stacki renames the file on disk, removing
the square brackets and dots that Astro uses to declare the route. No edit
and no save are involved — viewing the page is enough:

src/pages/kitchen-sink/[...path].astro   →   src/pages/kitchen-sink/-path-.astro

The transformation looks like [... → - and ] → -, so a named
parameter would go the same way:

[slug].astro        →   -slug-.astro
[...blog].astro     →   -blog-.astro

Git recorded it as a delete plus an untracked file:

 D src/pages/kitchen-sink/[...path].astro
?? src/pages/kitchen-sink/-path-.astro

The file contents were otherwise unchanged — a byte-for-byte match once
line endings are normalised (Stacki also converted LF → CRLF, which is
harmless here but may be worth knowing).

Why this is worse than a broken URL

The obvious effect is that the route stops existing and the page 404s.

The more serious effect is that renaming a dynamic route to a static one
silently disables getStaticPaths, because Astro only consults it for
dynamic routes.

We use that to keep a developer-only page out of production:

// src/pages/kitchen-sink/[...path].astro
export function getStaticPaths() {
  const on = import.meta.env.DEV || process.env.QA_PRIMITIVES === '1'
  return on ? [{ params: { path: undefined } }] : []
}

With the original filename, a production build correctly omits the page.
After the rename, the export is ignored and the page builds and ships:

dist/kitchen-sink/-path-/index.html    64 KB

That file contains a hardcoded http://127.0.0.1:8090 (our local CMS), and
the build exited 0 — no error, no warning. On a real deploy that would
have published an internal page to a client site.

Reproduction

1. In an Astro project, create src/pages/demo/[...path].astro with a
   getStaticPaths that returns [] unless import.meta.env.DEV.
2. Confirm astro build produces no dist/demo/.
3. Open the project in Stacki and open that page. Do not edit it, do not
   save, do not touch anything else.
4. The file on disk is now src/pages/demo/-path-.astro.
5. astro build now emits dist/demo/-path-/index.html.

Expected

Filenames should round-trip unchanged. Astro's [param], [...rest] and
[...rest].astro naming is load-bearing routing syntax, not decoration —
rewriting it changes what the project does.

If the current filename can't be represented internally, declining to open
that page would be much safer than opening it under a different name. A
read-only action should not rewrite the project.

Notes

• This happens on OPEN, not on save. The file is renamed as soon as the
  page is opened in the builder, with no edit made and nothing saved.
• Only the file I opened was affected. Other dynamic routes in the same
  project (src/pages/[...slug].astro, src/pages/blog/[slug].astro,
  src/pages/blog/[...blog].astro) were untouched.
• Recovering is straightforward once you notice — git checkout restores
  it — but nothing surfaces the problem at build time, which is what makes
  it easy to ship.

Happy to test a fix or provide any more detail.