`miden new` generates a project `miden build` rejects on 0.16.0: `[lib]` has no `path`

On the 0.16.0 toolchain, a freshly generated project does not build:

```console
$ miden new --account hesap
Created project /home/mustafa/fpi-test/hesap
$ cd hesap && miden build --release
`-> unable to parse project manifest: missing field `path`
,-[/home/mustafa/fpi-test/hesap/miden-project.toml:5:1]
4 |
5 | [lib]
: ^^^^^
6 | kind = "account-component"
`----
```

The generated `[lib]` section is just `kind` and `namespace`. Adding `path = "src/lib.rs"` to it makes the same project build. `--tx-script` generates the same shape and fails the same way.

The template in this repo is already correct: `extra/templates/rust/account/template/miden-project.toml` has carried `path = "src/lib.rs"` since ef7fe9b on 2026-08-07. The only templates release is `templates/v0.32.0-rc.1`, published 2026-08-06, one day earlier, which is presumably what `miden new` is still pulling.

So this looks like it needs a templates release rather than a code change.

Toolchain: `devnet` (0.16.0) installed through midenup 1.0.0-rc.1, `midenc 0.10.0-rc.1`, Linux x86_64.

The issue is in the project template used by `miden new`. Check the template files in `extra/templates/rust/account/template/miden-project.toml` and compare with the published template version. The fix is to ensure the `[lib]` section includes `path = "src/lib.rs"`. Verify the template release process and update the published templates if needed. Test by generating a new project and running `miden build`.

Written by the indexing model from the issue text.