feat: accept .reylo.yml as the project file's name - #13

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

ℹ️ No critical issues. One message that this change makes inaccurate is described below.

Reviewed changes

I reviewed the whole PR: the project file can now be named .reylo.yml as well as .reylo.yaml, and having both names beside one package.json is an error.

• Lookup: findProjectFile checks PROJECT_FILES in order, so .reylo.yaml wins. resolveProject reports an error when both files exist and REYLO_CONFIG is unset.
• Watching: watched now covers both names, and configIdentity already hashes resolved.error. So creating the second file retypes the project and shows the error.
• Mapper: a file ending in either name becomes export {};.
• Docs and examples: every contentMappers entry, plus the README, setup and configuration pages, now lists .reylo.yml.
• Tests: new coverage for the .yml name, watching both names, the both-files error and the REYLO_CONFIG bypass. The module test now imports a config/local.reylo.yml.

ℹ️ The strict_params diagnostic still names .reylo.yaml in a .reylo.yml project

The untyped-parameter error in src/module-types.ts:60 always says set strict_params: false in .reylo.yaml. In a project that uses .reylo.yml, it points to a file that doesn't exist. If the user follows it and creates .reylo.yaml, the project hits the new error .reylo.yaml and .reylo.yml are both project files; keep one. This PR already fixes the same problem for missingUrl, which uses file ? shown(file) : PROJECT_FILE, but this message can't do that because moduleTypes never gets the file name.

# strict_params diagnostic names a hardcoded `.reylo.yaml`

## Affected sites
- src/module-types.ts:60: message hardcodes `.reylo.yaml`
- src/mapper.ts:112: the only caller, `moduleTypes(sql, analysis, project.dialect, lexed, project.strictParams)`; it has the `Session`, whose `project.file` is the resolved path

## Required outcome
- When the project's file is `.reylo.yml` (or a `REYLO_CONFIG` path), the message names that file; with no project file, it keeps naming `.reylo.yaml` (`PROJECT_FILE`)
- Existing assertions in tests/strict-params.test.ts:77 keep passing for the `.reylo.yaml` case

## Suggested approach (optional)
- Pass the project file's display name (e.g. `basename(project.file ?? PROJECT_FILE)`) into `moduleTypes` next to `strictParams`, and use it in the message

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

ℹ️ The previous review's strict_params concern is fixed. One minor gap remains in the new reylo generate hint (see inline comment).

Reviewed changes

Since the last review at 6827cd2, one commit makes the project's messages name the file the project actually uses.

• Mapper option diagnostic: the code-104 message now names the resolved project file, given relative to the tsconfig's directory, instead of a fixed .reylo.yaml.
• strict_params diagnostic: moduleTypes now takes projectFile (it defaults to .reylo.yaml), and mapper.ts passes the project's file. This resolves the concern from the previous review.
• CLI hint: the "No query under …" message names the project's own file when the run opened exactly one project.
• Tests: tests/strict-params.test.ts now checks the code-12 message in a .reylo.yml project.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

✅ No new issues found. The reylo generate hint concern from the previous review is fixed.

Reviewed changes

Since the last review at 35ddb45, one commit makes the "No query under …" hint name a .reylo.yml project's file even when no .sql file was found.

• CLI hint fallback: when no session opened and at most one path was given, own is now findProjectFile(resolve(paths[0] ?? ".")). That function honours REYLO_CONFIG and checks both names beside the package's package.json. In every other case the hint still falls back to .reylo.yaml.
• Test: tests/cli.test.ts runs reylo generate in an empty .reylo.yml project and checks that the hint reads set cli.include in .reylo.yml.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}