change: Implement 1: Bootstrap the toolkit tree, project config and initial dependency lock #11
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: projects/product-54354138-1#11
Reference in New Issue
Block a user
Bootstrapped the repository-root toolkit tree required by the facade.
tools/__init__.py: minimal importable package exposing__version__only.tools/example.py: offline CLI (python -m tools.example REQUEST) that loads and validates a JSON request document with a validate-onlydry_runsemantics, prints exactly one structured JSON envelope (sorted keys) and fixes the status/exit vocabulary now (0 ok, 1 invalid request document, 2 usage error).--helpsupported.examples/input.json: canonical offline validate-only request document.tests/test_example.py: focused tests for the smoke command, envelope shape, request-document validation,--help, and the module entrypoint (13 tests).pyproject.toml: project metadata, setuptools build backend withpackages = ["tools"],devextra withpytest>=8.0, pytest optionspythonpath=["."]/testpaths=["tests"]so the repository root is importable.uv.lock: created through the supported dependency update operation for thetoolscomponent; pinned only from the approved dependency mirror (no public-index fallbacks, no credentials)..gitignore/.env.example: keep build artifacts out of the tree and document that no environment variables are required.Note:
requires-pythonwas raised to>=3.11because the approved mirror only offersexceptiongroup<1.0.0rc8, which cannot satisfy pytest on Python <3.11; the prepared environment (CPython 3.12.3) and CI bootstrap interpreter satisfy this. No protected facade paths were modified.Tests:
Ran the facade commands with the prepared environment (
.venv/bin/python):python -m compileall -q tools tests-> OK (tools.validate)python -m pytest -q-> 13 passed (tools.test)python -m tools.example examples/input.json-> single JSON envelope, exit 0 (tools.smoke)python -m tools.example --help-> usage text, exit 0 (help-command)Dependency lock/materialization performed via prepare_environment(component='tools', mode='update'): resolved + materialized,
uv.lockwritten. Target branchorigin/task/1-taskis already an ancestor of HEAD, so the branch contains the current target.Progress:
Created tools package (tools/__init__.py, tools/example.py), examples/input.json, tests/test_example.py, .gitignore, .env.example; updated pyproject.toml (metadata, setuptools packages, dev pytest extra, pytest pythonpath/testpaths, requires-python >=3.11 due to approved-mirror exceptiongroup constraint) and generated uv.lock via prepare_environment update. Facade validate/test/smoke and --help all pass locally.
Published by developer-agent through Tool Backend.
Closes #3
Developer-agent completed implementation and CI passed, but updating the PR title/body failed.
Intended title: change: Implement 1: Bootstrap the toolkit tree, project config and initial dependency lock
Commit:
d0b7f8f5aaCI: CI passed.
Intended body:
Bootstrapped the repository-root toolkit tree required by the facade.
tools/__init__.py: minimal importable package exposing__version__only.tools/example.py: offline CLI (python -m tools.example REQUEST) that loads and validates a JSON request document with a validate-onlydry_runsemantics, prints exactly one structured JSON envelope (sorted keys) and fixes the status/exit vocabulary now (0 ok, 1 invalid request document, 2 usage error).--helpsupported.examples/input.json: canonical offline validate-only request document.tests/test_example.py: focused tests for the smoke command, envelope shape, request-document validation,--help, and the module entrypoint (13 tests).pyproject.toml: project metadata, setuptools build backend withpackages = ["tools"],devextra withpytest>=8.0, pytest optionspythonpath=["."]/testpaths=["tests"]so the repository root is importable.uv.lock: created through the supported dependency update operation for thetoolscomponent; pinned only from the approved dependency mirror (no public-index fallbacks, no credentials)..gitignore/.env.example: keep build artifacts out of the tree and document that no environment variables are required.Note:
requires-pythonwas raised to>=3.11because the approved mirror only offersexceptiongroup<1.0.0rc8, which cannot satisfy pytest on Python <3.11; the prepared environment (CPython 3.12.3) and CI bootstrap interpreter satisfy this. No protected facade paths were modified.Tests:
Ran the facade commands with the prepared environment (
.venv/bin/python):python -m compileall -q tools tests-> OK (tools.validate)python -m pytest -q-> 13 passed (tools.test)python -m tools.example examples/input.json-> single JSON envelope, exit 0 (tools.smoke)python -m tools.example --help-> usage text, exit 0 (help-command)Dependency lock/materialization performed via prepare_environment(component='tools', mode='update'): resolved + materialized,
uv.lockwritten. Target branchorigin/task/1-taskis already an ancestor of HEAD, so the branch contains the current target.Published by developer-agent through Tool Backend.
Scaffold PR is complete and verified on the exact head SHA. The toolkit tree (tools/__init__.py, tools/example.py), examples/input.json, tests/test_example.py, updated pyproject.toml and a mirror-only uv.lock are present; no protected facade paths were touched. CI on
d0b7f8fran restore (status=prepared), compileall, pytest (13 passed) and the smoke command (single JSON envelope, exit 0), plus the facade help-command acceptance.Findings:
.env.exampledocuments LOG_LEVEL, but tools/example.py never reads any environment variable; the file matches the facade's optional LOG_LEVEL declaration, so this is informational only.EXIT_USAGE = 2is exported but no test asserts the usage-error path (e.g. invokingpython -m tools.examplewith no REQUEST). argparse's own exit code 2 matches the documented vocabulary, so the contract is not violated..agent/project.yamldeclares the facade acceptanceimport-package(package_import), but the generated workflow only materializesacceptance.help-command;read_ci_log.ci_resultscontains no record forimport-package. This task's change contract declares no facade_acceptance_refs, so it is not required here, but final task-branch/product acceptance should not assume package-import acceptance was exercised.tools.dependencies.resolutionis skipped by the generated workflow ('not declared'); the lockfile is nevertheless proven usable because lockfile-present is satisfied and tools.dependencies.restore materialized the environment from uv.lock through the internal mirror only.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint. (tests/test_example.py:1-118; tests:1-1; CI job 2:315-392)uv sync --lockedagainst the internal mirror, reporting status=prepared and installing pytest 8.3.3 from the lock. (pyproject.toml:1-23; uv.lock:1-63; CI job 2:315-392)Scaffold task is complete and verified on head
d0b7f8f5aa. The toolkit tree (tools/__init__.py, tools/example.py), examples/input.json, tests/test_example.py (13 tests), updated pyproject.toml and a mirror-only uv.lock are all present at the reviewed commit; protected facade/control paths (.agent/project.yaml, .agent/acceptance.yaml, .gitea/workflows/) are untouched. Exact-head CI ran the facade contract: tools.dependencies.restore (status=prepared, 5 packages installed from uv.lock), tools.validate (compileall of all three modules), tools.test (13 passed under pytest with pyproject.toml as configfile), tools.smoke (single JSON envelope, exit 0) and acceptance.help-command (usage text, exit 0). Task-local artifact/capability criteria are all satisfied; remaining items are non-blocking observations.Findings:
acceptance.help-command. The facade (.agent/project.yaml:141-147) also declaresimport-package(package_import), and read_ci_log.ci_results at this SHA has no record with target_id=import-package. This task's change contract declares no facade_acceptance_refs/verification_execution, so it is not required for this developer PR, but final task-branch/product acceptance must not assume package-import acceptance was exercised..env.exampledocuments LOG_LEVEL, but tools/example.py reads no environment variable; the file matches the facade's optional LOG_LEVEL declaration (project.yaml:45-52), so it is informational only.EXIT_USAGE = 2is exported (tools/example.py:25,35) but no test asserts the usage-error path (e.g. invokingpython -m tools.examplewith no REQUEST). argparse's own exit code 2 matches the documented vocabulary, so the exit contract is not violated, only unasserted.requires-pythonwas raised to>=3.11(pyproject.toml:10) and uv.lock mirrors it (uv.lock:3), which is internally consistent (pytest resolves without exceptiongroup/tomli). This narrows supported interpreters relative to the barepyproject.tomlplaceholder and is not yet documented in README.md; worth recording in the product docs before final delivery.tools.dependencies.resolutionis skipped by the generated workflow ('not declared', CI line 334); lockfile usability is nevertheless proven because the lock exists and tools.dependencies.restore performeduv sync --lockedsuccessfully from the internal mirror only.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint with pyproject.toml as configfile. (tests/test_example.py:1-118; tests:1-1; CI job 2:315-392)uv sync --lockedfrom the internal mirror (pytest 8.3.3 and deps installed, status=prepared, exit 0) with the lock's requires-python matching the manifest. (pyproject.toml:1-23; uv.lock:1-63; CI job 2:315-392)Scaffold PR for issue #3 is complete and verified on head
d0b7f8f5aa. The toolkit tree (tools/__init__.py, tools/example.py), examples/input.json, tests/test_example.py, the extended pyproject.toml and a mirror-only uv.lock are all present at the reviewed commit. No protected facade/control path appears in the changed-file set (only .agent-work/ledger.json, .env.example, .gitignore, examples/input.json, pyproject.toml, tests/test_example.py, tools/*, uv.lock), so .agent/project.yaml and .gitea/workflows/ci.yaml remain the provisioned versions. Exact-head CI ran the facade contract for this component: tools.dependencies.restore (uv sync --locked from the internal mirror, status=prepared, pytest 8.3.3 + 4 deps installed), tools.validate (compileall of all three modules, exit 0), tools.test (13 passed, pyproject.toml as configfile), tools.smoke (single sorted-key JSON envelope, exit 0) and acceptance.help-command (usage text, exit 0). All eight task-local artifact/capability criteria are backed by repository artifacts plus passing CI on this SHA. Remaining items are non-blocking observations to carry into later/final acceptance.Findings:
.agent/project.yaml:141-147declares facade acceptanceimport-package(kind package_import, component tools, package tools), but the generated workflow materializes onlyacceptance.help-command;read_ci_log.ci_resultsat this SHA has no record with target_id=import-package. This task's change contract declares no facade_acceptance_refs/verification_execution, so it is not required for this developer PR, but follow-up generations and final task-branch/product acceptance must not assume package-import acceptance was exercised.tools.dependencies.resolutionis skipped by the generated workflow ("not declared", CI line 334); lockfile usability is nevertheless proven because lockfile-present holds andtools.dependencies.restoreperformed a locked sync from the internal mirror only.EXIT_USAGE = 2is exported (tools/example.py:25,35) but no test asserts the usage-error path (e.g.python -m tools.examplewith no REQUEST); argparse's own exit code 2 matches the documented vocabulary, so the exit contract holds but is unasserted..env.exampledocuments LOG_LEVEL while tools/example.py reads no environment variable; this matches the facade's optional LOG_LEVEL declaration (.agent/project.yaml:49-52), so it is informational only.requires-python = ">=3.11"(pyproject.toml:10) narrows the interpreter range relative to the bare placeholder and is internally consistent with uv.lock:3 and the CI interpreter (CPython 3.12.3), but the constraint is not yet reflected in README.md; worth documenting before final delivery.Findings:
import-package(package_import) acceptance (.agent/project.yaml:141-147) but the generated workflow only materializes acceptance.help-command; ci_results at this SHA has no target_id=import-package record. Not required for this developer PR (no facade_acceptance_refs in the change contract), but final acceptance must not treat package-import as exercised.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint with pyproject.toml as configfile. (tests/test_example.py:1-118; tests:1-1; CI job 2:314-392)uv sync --lockedfrom the internal mirror (status=prepared, 5 packages installed, pytest 8.3.3) with admission subject hashes for .agent/project.yaml, pyproject.toml and uv.lock. (pyproject.toml:1-23; uv.lock:1-63; CI job 2:314-392)Scaffold PR for issue #3 is complete and verified on head
d0b7f8f5aa. The toolkit tree (tools/__init__.py, tools/example.py: the offline request-document CLI with a single sorted-key JSON envelope and fixed exit vocabulary), examples/input.json, tests/test_example.py, the extended pyproject.toml and a mirror-only uv.lock are all present at the reviewed commit. No protected facade/control path appears in the changed-file set (only .agent-work/ledger.json, .env.example, .gitignore, examples/input.json, pyproject.toml, tests/test_example.py, tools/*, uv.lock), so .agent/project.yaml and .gitea/workflows/ci.yaml remain the provisioned versions. Exact-head CI ran the facade contract: tools.dependencies.restore (status=prepared, 5 packages installed from uv.lock via the internal mirror), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed with pyproject.toml as configfile) and tools.smoke (single JSON envelope, exit 0), plus the facade help-command acceptance (usage text, exit 0). All eight supplied task-local artifact/capability criteria are backed by repository artifacts plus passing CI on this SHA; the remaining items are non-blocking observations for later/final acceptance.Findings:
import-package(package_import, component tools, package tools), but the generated workflow only materializesacceptance.help-command; read_ci_log.ci_results at this SHA contains records only for tools.dependencies.restore, tools.validate, tools.test, tools.smoke and acceptance.help-command. This task's change contract declares no facade_acceptance_refs/verification_execution, so it is not required for this developer PR, but final task-branch/product acceptance must not assume package-import acceptance was exercised.tools.dependencies.resolutionis skipped by the generated workflow ('skip tools.dependencies.resolution (not declared)'); lockfile usability is nevertheless proven because uv.lock is committed and tools.dependencies.restore performed a locked sync from the internal mirror only.EXIT_USAGE = 2is exported (tools/example.py:25,35) but no test asserts the usage-error path (e.g.python -m tools.examplewith no REQUEST); argparse's own exit code 2 matches the documented vocabulary, so the exit contract holds but is unasserted..env.exampledocuments LOG_LEVEL while tools/example.py reads no environment variable; this matches the facade's optional LOG_LEVEL declaration, so it is informational only.requires-python = ">=3.11"(pyproject.toml:10, uv.lock:3) narrows supported interpreters relative to the base manifest and is consistent with the CI interpreter (CPython 3.12.3), but it is not yet reflected in README.md; worth documenting before final delivery.setuptools>=68from [build-system] is not pinned in uv.lock (which contains only the 5 runtime/dev packages plus the editable root), so the backend used for the editable build is resolved outside the locked set; the exact-head restore still built and installed the project successfully.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile. (tests/test_example.py:1-118; .:1-11; CI job 2:315-392)uv sync --lockedfrom the internal mirror (status=prepared, 5 packages installed including pytest 8.3.3, command_exit_code 0) with admission subject hashes for .agent/project.yaml, pyproject.toml and uv.lock. (pyproject.toml:1-23; uv.lock:1-63; CI job 2:315-392)Scaffold PR for issue #3 satisfies all eight task-local criteria on head
d0b7f8f5aa. The toolkit tree (tools/__init__.py, tools/example.py), examples/input.json, tests/test_example.py, extended pyproject.toml and a mirror-only uv.lock exist and are exercised by exact-head CI: tools.dependencies.restore (status=prepared from uv.lock), tools.validate (compileall exit 0), tools.test (13 collected / 13 passed, pyproject.toml as configfile), tools.smoke (single JSON envelope, exit 0) and acceptance.help-command (facade_acceptance help-command, passed). No protected facade/control path is modified (.agent/project.yaml hash still matches the provisioned sha256). Verdict: approve and merge.Findings:
python -m tools.examplewith no REQUEST); argparse's own exit code 2 matches the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile. (tests/test_example.py:1-118; tests:1-1; CI job 2:315-392)Scaffold PR for issue #3 satisfies all eight task-local artifact/capability criteria on head
d0b7f8f5aa. tools/__init__.py, tools/example.py (offline request-document CLI with a single sorted-key JSON envelope and fixed exit vocabulary), tests/test_example.py, examples/input.json, the extended pyproject.toml and a mirror-only uv.lock all exist and are exercised by exact-head CI: tools.dependencies.restore (status=prepared, locked sync from the internal mirror, pytest 8.3.3 installed), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed with pyproject.toml as configfile), tools.smoke (single JSON envelope, exit 0) and acceptance.help-command (facade_acceptance help-command, passed). No protected facade/control path is touched — the changed-file set contains only .agent-work/ledger.json, .env.example, .gitignore, examples/input.json, pyproject.toml, tests/test_example.py, tools/* and uv.lock, and the CI restore admission record for .agent/project.yaml still carries the provisioned sha256 02a8118a…. Verdict: approve and merge.Findings:
python -m tools.examplewith no REQUEST); argparse's own exit code 2 matches the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile; tools.validate also compiled it. (tests/test_example.py:1-118; .:1-11; CI job 2:315-392)Scaffold PR for issue #3 is complete and verified on head
d0b7f8f5aa. tools/__init__.py (version-only package), tools/example.py (offline request-document CLI emitting one sorted-key JSON envelope with the fixed 0/1/2 exit vocabulary), tests/test_example.py (13 tests), examples/input.json (validate-only dry_run request), extended pyproject.toml and a mirror-only uv.lock all exist at the reviewed commit. No protected facade/control path is in the change set, and the CI restore admission record still carries the provisioned .agent/project.yaml sha256 02a8118a…, so the facade was not weakened or edited. Exact-head CI ran the full facade contract for component tools: tools.dependencies.restore (status=prepared,uv sync --lockedfrom the internal mirror, pytest 8.3.3 + iniconfig/packaging/pluggy/colorama installed, command_exit_code 0), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed with pyproject.toml as configfile), tools.smoke (single JSON envelope {"command": "example", "dry_run": true, "mode": "validate", "request": "examples/input.json", "status": "ok", "version": 1}, exit 0) and facade acceptance help-command (usage text, exit 0). All eight supplied task-local artifact/capability criteria are satisfied; remaining items are non-blocking observations for later/final acceptance. Verdict: approve and merge.Findings:
python -m tools.examplewith no REQUEST); argparse supplies exit code 2, matching the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile, and compileall compiled it. (tests/test_example.py:1-118; CI job 2:315-392)uv sync --lockedfrom the internal dependency mirror, status=prepared, 5 packages installed including pytest 8.3.3, command_exit_code 0) with admission subject hashes for .agent/project.yaml, pyproject.toml and uv.lock. (pyproject.toml:1-23; uv.lock:1-63; CI job 2:315-392)Scaffold PR for issue #3 satisfies all eight task-local artifact/capability criteria at head
d0b7f8f5aa. The toolkit tree (tools/__init__.py, tools/example.py with a single sorted-key JSON envelope and fixed 0/1/2 exit vocabulary), tests/test_example.py (13 tests), examples/input.json (validate-only dry_run request), extended pyproject.toml and a mirror-only uv.lock all exist at the reviewed commit. No protected facade/control path is in the change set, and the CI restore admission record still carries the provisioned .agent/project.yaml sha256 02a8118a…, so the facade was not edited or weakened. Exact-head CI ran the facade contract: tools.dependencies.restore (status=prepared,uv sync --lockedfrom the internal mirror, pytest 8.3.3 + deps + editable root installed, exit 0), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed, pyproject.toml as configfile), tools.smoke (single JSON envelope, exit 0) and facade acceptance help-command (target_id=help-command, passed). Verdict: approve and merge into task/1-task.Findings:
python -m tools.examplewith no REQUEST); argparse supplies exit code 2, matching the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile, and tools.validate compiled it. (tests/test_example.py:1-118; tests:1-1; CI job 2:290-392)uv sync --lockedfrom the internal dependency mirror, status=prepared, 5 packages installed including pytest 8.3.3, command_exit_code 0) with admission subject hashes for .agent/project.yaml (provisioned 02a8118a…), pyproject.toml and uv.lock. (pyproject.toml:1-23; uv.lock:1-63; .agent/project.yaml:1-160; CI job 2:290-392)Scaffold PR for issue #3 satisfies all eight supplied artifact/capability criteria at head
d0b7f8f5aa. tools/__init__.py, tools/example.py (offline request-document CLI emitting one sorted-key JSON envelope with the fixed 0/1/2 exit vocabulary), tests/test_example.py (13 tests), examples/input.json, extended pyproject.toml and a mirror-only uv.lock all exist and are exercised by exact-head CI: tools.dependencies.restore (status=prepared, locked sync from the internal mirror, pytest 8.3.3 installed, exit 0), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed, pyproject.toml as configfile), tools.smoke (single JSON envelope, exit 0) and facade acceptance help-command (target_id=help-command, passed). No protected facade/control path is in the change set (.agent/project.yaml and .gitea/workflows are untouched; only .agent-work/ledger.json, .env.example, .gitignore, examples/input.json, pyproject.toml, tests/test_example.py, tools/*, uv.lock changed). Remaining items are non-blocking observations for later/final acceptance. Verdict: approve and merge into task/1-task.Findings:
python -m tools.examplewith no REQUEST); argparse supplies exit code 2, matching the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile, and compileall also compiled it. (tests/test_example.py:1-118; CI job 2:315-392)Scaffold PR for issue #3 satisfies all eight supplied artifact/capability criteria at head
d0b7f8f5aa. tools/__init__.py (version-only package), tools/example.py (offline request-document CLI emitting exactly one sorted-key JSON envelope with the fixed 0/1/2 exit vocabulary), tests/test_example.py (118 lines, 13 tests), examples/input.json (validate-only dry_run request), extended pyproject.toml and a mirror-only uv.lock all exist at the reviewed commit. No protected facade/control path is in the change set, and the restore admission subject still carries the provisioned .agent/project.yaml sha256 02a8118a…, so the facade was not edited or weakened. Exact-head CI ran the facade contract: tools.dependencies.restore (status=prepared, uv sync --locked from the internal mirror, pytest 8.3.3 + deps + editable root installed, command_exit_code 0), tools.validate (compileall of all three modules, exit 0), tools.test (13 collected / 13 passed with pyproject.toml as configfile, no skips) and tools.smoke (single JSON envelope, exit 0), plus facade acceptance help-command (target_id=help-command, passed). Verdict: approve and merge into task/1-task.Findings:
python -m tools.examplewith no REQUEST); argparse supplies exit code 2, matching the documented vocabulary, so the contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile, and compileall compiled it. (tests/test_example.py:1-118; tests:1-1; CI job 2:280-392)Scaffold PR for issue #3 satisfies all eight supplied task-local artifact/capability criteria at head
d0b7f8f5aa. tools/__init__.py (version-only package), tools/example.py (offline request-document CLI emitting exactly one sorted-key JSON envelope with the fixed 0/1/2 exit vocabulary), tests/test_example.py (118 lines, 13 tests), examples/input.json (validate-only dry_run request), extended pyproject.toml and a mirror-only uv.lock all exist at the reviewed commit. No protected facade/control path is in the change set (.agent/project.yaml, .agent/acceptance.yaml and .gitea/workflows/ are untouched; the diff is limited to .agent-work/ledger.json, .env.example, .gitignore, examples/input.json, pyproject.toml, tests/test_example.py, tools/*, uv.lock), and the restore admission subject still carries the provisioned .agent/project.yaml sha256 02a8118a…, so the facade was not edited or weakened. Exact-head CI ran the facade contract for component tools: tools.dependencies.restore (status=prepared, 5 packages installed + editable root built, command_exit_code 0), tools.validate (compileall of all three modules, status=passed), tools.test (13 collected / 13 passed with pyproject.toml as configfile, no skips), tools.smoke (single JSON envelope, status=passed) and facade acceptance help-command (target_id=help-command, status=passed). tools.dependencies.resolution is skipped by the generated workflow ("not declared"), but lockfile usability is proven by the successful locked restore from uv.lock through the internal mirror only. Verdict: approve and merge into task/1-task.Findings:
python -m tools.examplewith no REQUEST); argparse supplies exit code 2, matching the documented vocabulary, so the exit contract holds but is unasserted.Acceptance evidence for
d0b7f8f5aa2df831b5bfce585314f0edb3b5608d:pytestCI entrypoint collected 13 items and reported 13 passed with pyproject.toml as configfile, and compileall also compiled it. (tests/test_example.py:1-118; CI job 2:315-392)