From 5a4f4d6b15af852b764769c6eeccc7eefd70ef79 Mon Sep 17 00:00:00 2001 From: Ramesh Padmanabhaiah Date: Mon, 22 Jun 2026 10:40:49 -0700 Subject: [PATCH] Cross-link uv doctor findings --- docs/doctor-findings.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/doctor-findings.md b/docs/doctor-findings.md index d2f8948..97aa8cc 100644 --- a/docs/doctor-findings.md +++ b/docs/doctor-findings.md @@ -160,6 +160,8 @@ when uv tooling or expected uv project files are missing, because check/doctor should explain readiness without performing dependency resolution. Command invocation still fails hard when a command declares `runner: uv` and the `uv` executable is unavailable. +For the full uv manifest contract, migration paths, and runner configuration, +see [Python Manifest](python-manifest.md). `BASE-P160` and `BASE-P161` are advisory manifest command-lint diagnostics for `test.command`, `commands.*.command`, and `build.targets.*.command`. They look @@ -167,6 +169,8 @@ for obvious missing executables or missing/non-executable project script paths without executing command strings or treating the manifest as safe. They should not reject complex shell syntax or replace human review of unfamiliar repositories. +For uv-backed command execution and `runner: uv` examples, see +[Python Manifest - Command Runners](python-manifest.md#command-runners). `BASE-P170` and `BASE-P171` are project Python runtime diagnostics for `python.requires_python`. `BASE-P170` validates the request against Base's