This is the concise contributor landing page. Use it to set up a worktree, choose the right validation tier, and find the canonical procedure. The developer guide index organizes architecture, planner, scenario, tooling, and research-facing topics; the detailed compatibility reference preserves older deep links while procedures migrate to focused guides.
- Read
AGENTS.mdanddocs/maintainer_values.mdfor precedence, safety, evidence, and worktree rules. - Check host capabilities with
docs/dev_runtime_requirements.md, then run the setup below. - Create a linked worktree before editing, pushing, or running PR validation. Follow the worktree lifecycle guide.
- Pick the cheapest validation tier that proves the change. Use the local-CI guide for shared helpers and PR readiness.
scripts/dev/check_runtime_requirements.sh
uv sync --all-extras
source .venv/bin/activate
uv run pre-commit install
uv run python -c "from robot_sf.gym_env.environment_factory import make_robot_env; print('Import successful')"Use uv sync for the core environment or a named extra when the touched path needs optional
dependencies. uv sync --all-extras is the canonical complete local setup; CARLA remains an
explicit opt-in group for CARLA-capable worktrees.
| Change | Minimum proof | Canonical entry point |
|---|---|---|
| Docs or instructions | Diff, changed links/paths, lightweight docs checks | scripts/dev/check_docs_evidence_integrity.py |
| Workflow, helper, or skill | Focused tests plus schema/sync checks | docs/dev/local_ci.md |
| Runtime code | Focused tests, Ruff, and format | scripts/dev/run_tests_parallel.sh |
| Benchmark, metric, schema, provenance, or paper claim | Executable proof with provenance and caveats | docs/code_review.md |
Escalate to BASE_REF=origin/main scripts/dev/pr_ready_check.sh for scripts, schemas, generated
indexes, routing, runtime, benchmark, metric, provenance, or paper-facing changes. Fallback or
degraded execution is diagnostic only, never success evidence.
Coverage remains opt-in locally. The coverage-gate and changed-coverage-gate CI jobs combine
their shard data and enforce the workflow's configured thresholds; the local wrapper is configured
to measure only the robot_sf/ package. Auxiliary fast-pysf sources are not included in wrapper reports.
CI publishes the changed-coverage.v1 result for changed-file enforcement, while coverage-gate
enforces the configured 85.0% total threshold. The coverage configuration omits fast-pysf/tests/*
and fast-pysf/examples/* from the measured source scope. See the coverage guide
for source scope, reports, and explicit coverage commands.
- Worktree lifecycle — create, bootstrap, validate, preserve, and retire linked worktrees safely.
- Local CI and PR readiness — dependency profiles, shared environments, scratch capacity, focused tests, and final readiness.
- Agent workflow entrypoints — canonical
uv runand validation commands. - Batch-first issue workflow — issue and
Project #5 batching rules. Canonical path:
docs/context/issue_713_batch_first_issue_workflow.md. - Coding-agents compatibility note — retrieval, planning, execution, and verification across providers.
- Developer guide index — architecture and contribution navigation.
- Runtime requirements and environment setup.
- Benchmark governance, research guide, and code review guide.
- Coverage guide, quality report guide, and dev scripts.
- Canonical skills live in
.agents/skills/; use the skill'sSKILL.mdfor task-specific execution contracts. - The current Issue #5303 promotion entrypoint is
scripts/tools/check_issue_5303_search_promotion_contract_v2.py --identities; its identity mode is side-effect-free and the historical v1 path cannot authorize promotion.
These short stubs preserve common inbound links from examples, docs, and older checkouts. The
procedure itself lives in the detailed reference or the linked canonical guide. The complete
source-to-target inventory is dev_guide_anchor_migration.yaml.
See the examples quickstart walkthrough.
See the environment factory procedure.
See the advanced feature and policy examples.
See the advanced feature and policy examples.
See the environment factory procedure.
See the advanced feature demos.
See the planner selection procedure.
See the coverage workflow and the detailed coverage section.
See the unified test-suite section.
See the CI/CD expectations and local-CI guide.
See the run tracker procedure.
See the performance budget.
This placeholder preserves the example fragment used by documentation templates; link to a named section in the developer guide index instead.
Keep this landing page focused on first-use decisions and compatibility stubs. Add detailed
procedures to an existing canonical topic owner or a new task guide only when no owner exists, then
link it from docs/developer-guide.md. Do not copy a second full workflow
back into this file.