Fix check crash and raw render error on unreadable project dirs

[cderv]

When a _quarto.yml is left in the home directory by accident, every path under ~ becomes part of one project. Input discovery then walks all of ~, and on the first directory Quarto cannot read (Photos Library.photoslibrary on macOS in #14960) the command fails with a raw PermissionDenied ... readdir error and a stack trace. This happens also with quarto check, which is the command a user runs to understand what is wrong. I reproduced it on Windows with an icacls deny on a directory inside the project.

New improved behavior

• New quarto check info output

❯ quarto.cmd check info
Quarto 99.9.9
[>] Checking environment information...
      Quarto cache location: C:\Users\chris\AppData\Local\quarto
      Project root: C:\Users\chris\Documents\DEV_R\quarto-cli.worktrees\issue-14960\tests\docs\smoke-all\book\htmlbook
      Project config: C:\Users\chris\Documents\DEV_R\quarto-cli.worktrees\issue-14960\tests\docs\smoke-all\book\htmlbook\_quarto.yml

• when there is a directory problem

ERROR: Could not read a directory while looking for project input files.
x Accès refusé. (os error 5): readdir 'C:\Users\chris\AppData\Local\Temp\quarto-error-demo-f7214f580f0148aeb3fd58861e8c895e\locked'
i Project root: C:\Users\chris\AppData\Local\Temp\quarto-error-demo-f7214f580f0148aeb3fd58861e8c895e
i Set by: C:\Users\chris\AppData\Local\Temp\quarto-error-demo-f7214f580f0148aeb3fd58861e8c895e\_quarto.yml
i If this _quarto.yml was created by accident, remove it. Otherwise make the directory readable.

Root Cause

quarto check builds a full projectContext() only to read config.engines (initializeProjectContextAndEngines() in src/command/command-utils.ts). So it runs the input walk and creates <root>/.quarto, while nothing in check uses input files. The walk has no error handling, so render and preview show the Deno error as is.

Fix

• resolveProjectConfig() is extracted from projectContext(): upward _quarto.yml resolution and the whole config block (profiles, engine extensions, dotenv, vars, translations). projectContext() calls it and then walks as before. check, create, create-project and call engine now use only the config part, so they don't walk inputs or create <root>/.quarto anymore. The config block is kept whole so check sees the same engines and profiles as render.
• quarto check info reports the project root and the _quarto.yml that set it (info.project = { dir, configFile } in JSON, null outside a project), and warns when the root is the home directory or a filesystem root.
• The input walk and project.render glob expansion tag a PermissionDenied with the project dir and config file, and rethrow the same error. render and preview turn a tagged error into one framed error without stack, with the unreadable dir, the project root, the _quarto.yml and a hint that it may have been created by accident. inspect is unchanged on purpose, it is machine-read and must be complete or fail.
• When the walk throws, the project context now closes its .quarto cache and session temp dir before rethrowing.

We don't skip unreadable dirs anywhere. A render or inspect that is silently incomplete is worse than failing.

llm-docs/project-context-architecture.md documents how the project context is resolved and the cache lifecycle.

Test Plan

• check, inspect, project, output-dir, freeze and preview tests pass locally on Windows (30 files, 81 tests)
• check from a subdir of a project with an unreadable dir succeeds and reports the project, and creates no <root>/.quarto
• check info JSON info.project inside and outside a project, home-dir warning through a HOME/USERPROFILE overlay
• render and project.render glob expansion fail with the framed error, inspect keeps the raw error
• Framed error has no stack: printStack=false is pinned in tests/unit/project/project-context-unreadable-dir.test.ts. Dev builds always set QUARTO_DEBUG=true, so the smoke test ignores the appended stack. Checked by hand with QUARTO_DEBUG=false for render, preview of a file and preview of a dir.
• CI on Linux and Windows. macOS is not in CI, so the chmod 000 path is only exercised on Ubuntu and macOS is untested.

The unreadable-dir fixture uses an icacls deny on Windows and chmod 000 elsewhere. These tests are not registered when running as root. GitHub Ubuntu runners are non-root, so CI enforces the denial. Deno's resource sanitizer can't be used in unitTest, the harness itself leaks a file handle and a timeout timer. So the cache cleanup test relies on os error 32 on Windows, plus a check on all OSes that no .quarto/quarto-session-temp* is left behind.

Depends on #14965

Fixes #14960

[posit-snyk-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.