write-manifest records an absolute --requirements-file path in manifest.json, breaking the server build #900

🤖 write-manifest with an absolute -r/--requirements-file path writes that absolute path into manifest.json. The bundle then doesn't match on the server, and the build fails. A relative path works.

Repro

mkdir p && cd p
printf 'from flask import Flask\napp = Flask(__name__)\n' > app.py
echo flask > reqs.txt
rsconnect write-manifest api -r "$PWD/reqs.txt" .
python3 -c "import json; d = json.load(open('manifest.json')); print(d['python']['package_manager']['package_file'], list(d['files']))"

/abs/path/p/reqs.txt ['/abs/path/p/reqs.txt', 'app.py', 'reqs.txt']

deploy manifest manifest.json then fails during the Connect build. The same output also warns /abs/path/p/reqs.txt already exists and will not be overwritten.

Expected

Normalize the requirements path relative to the project directory (and reject paths outside it).

Found during live QA of #892 against Posit Connect. Reproduced on 1.32.0 and current main (0287aca3).