specfuse/loop

No problems traced to this repository code in these checks.

OSV scanned supported lockfiles; unpinned dependencies and unsupported formats are outside this check.

A short run cannot establish that code is safe.

Connections show IP addresses; proxies can hide the final hostname.

Tracing covers dispatched commands and their children, not the whole OS; guest root can interfere with tracing.

Full safety evidence →

• The README says the worked example feature can be linted with lint_plan.py: Real input produced the expected result: structurally valid

  Source: python .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint

  Input: .specfuse/features/FEAT-2026-0001-health-endpoint

  Expected: structurally valid

  Command: python3 .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint

  Observed: …structurally valid.

Examples

• Lint the self-demonstrating worked example feature: command completed successfully

  Source: README.md Layout/self-demonstrating reference installation

  Input: .specfuse/features/FEAT-2026-0001-health-endpoint

  Expected: structurally valid

  Command: python3 .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint

  Observed: PLAN.md: missing 'planned_cost_usd' frontmatter (optional but recommended for cost-variance calibration). See PLAN.md roadmap_goal § Planned-cost capture. WARN: .specfuse/features/FEAT-2026-0001-health-endpoint/WU-93-gate-1-plan-next.md: body does not instruct the agent to produce `GATE-02-REVIEW.md` (assert_gate_review_exists names the review for the gate being DRAFTED, not the one being closed). assert_gate_review_exists checks this AFTER dispatch, so the refusal costs a full re-attempt. See close-discipline.md §4. OK — .specfuse/features/FEAT-2026-0001-health-endpoint is structurally valid.

Local or hosted: local

Install specfuse via pip, scaffold a project with specfuse init, and lint the worked example feature with the README's lint_plan.py command

cd <guest-path> && ls -la && git status 2>&1 | head -3; python3 --version; echo; cat README.md 2>/dev/null | head -c 6000
cd <guest-path> && tail -c +6000 README.md | head -c 4000; echo ----; grep -n -i "requires-python\|^name\|scripts" -A3 pyproject.toml | head -40; echo ----; ls .coldpass; which pipx uv; sudo -n true && echo SUDO_OK
cd /tmp && python3 -m venv <guest-path> && <guest-path> -m pip install -q --upgrade pip 2>&1 | tail -3; <guest-path> -m pip install specfuse 2>&1 | tail -5; ls <guest-path> | grep -i specfuse
cd <guest-path> && <guest-path> init --help 2>&1 | head -40; echo "---"; ls -la <guest-path>
cd <guest-path> && <guest-path> init --no-self-upgrade <guest-path> 2>&1 | tail -30; echo "rc=${PIPESTATUS[0]}"; ls -la <guest-path> 2>&1 | head -30
mkdir -p <guest-path> && cd <guest-path> && <guest-path> init --no-self-upgrade <guest-path> 2>&1 | tail -30; echo "rc=${PIPESTATUS[0]}"; find <guest-path> -maxdepth 3 | head -40
cd <guest-path> && python3 .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint 2>&1 | tail -20; echo "rc=${PIPESTATUS[0]}"; echo ----; python3 .specfuse/scripts/loop.py --dry-run 2>&1 | tail -40; echo "rc=${PIPESTATUS[0]}"
cd <guest-path> && <guest-path> .specfuse/features/FEAT-2026-0001-health-endpoint 2>&1 | tail -2; echo "rc=${PIPESTATUS[0]}"; echo ----; cd <guest-path> && <guest-path> run --dry-run 2>&1 | tail -6; echo "rc=${PIPESTATUS[0]}"; echo ----; cd <guest-path> && grep -rn -i "\-\-once\|\-\-now\|cron\|webhook" .specfuse/scripts/loop.py | head -10; grep -n "add_argument" .specfuse/scripts/loop.py | head -30
mkdir -p <guest-path> && cd <guest-path> && cat > probe.json <<'EOF'
{"kind":"cli","argv":["python3",".specfuse/scripts/lint_plan.py",".specfuse/features/FEAT-2026-0001-health-endpoint"],"cwd":"<guest-path>","expected_text":"structurally valid"}
EOF
cat > claims.json <<'EOF'
[{"kind":"claim","claim":"The README says the worked example feature can be linted with lint_plan.py","source":"python .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint","input":".specfuse/features/FEAT-2026-0001-health-endpoint","expected":"structurally valid","probe_kind":"cli","argv":["python3",".specfuse/scripts/lint_plan.py",".specfuse/features/FEAT-2026-0001-health-endpoint"],"expected_text":"structurally valid","cwd":"<guest-path>"}]
EOF
cat > examples.json <<'EOF'
[{"kind":"example","claim":"Lint the self-demonstrating worked example feature","source":"README.md Layout/self-demonstrating reference installation","input":".specfuse/features/FEAT-2026-0001-health-endpoint","expected":"structurally valid","argv":["python3",".specfuse/scripts/lint_plan.py",".specfuse/features/FEAT-2026-0001-health-endpoint"],"cwd":"<guest-path>","env":{},"expected_text":"structurally valid"}]
EOF
cat > cycles.json <<'EOF'
{"detected":false,"checks":[],"reason":"Inspected README.md and specfuse-loop entrypoints (.specfuse/scripts/loop.py, specfuse run). No cron, webhook, --once or --now scheduler is documented; specfuse run is a manual gate-walk driver, and its only offline mode (--dry-run) fails here with 'No active feature' because no PLAN.md is status active."}
EOF
for f in probe claims examples cycles; do <guest-path> -m json.tool $f.json >/dev/null 2>&1 || python3 -c "import json,sys;json.load(open('$f.json'))" && echo "$f ok"; done
mkdir -p <guest-path> && cd <guest-path> && cat > report.json <<'EOF'
{"outcome":"working","fault_owner":null,"operation":"Install specfuse via pip, scaffold a project with specfuse init, and lint the worked example feature with the README's lint_plan.py command","operation_scope":"Python 3.12.3 (requires >=3.10), venv at <guest-path>, no network upgrade (--no-self-upgrade), no Claude Code plugin, no git metadata","steps":["python3 -m venv <guest-path> && <guest-path> -m pip install specfuse (README: python3 -m pip install specfuse, in a venv)","mkdir -p <guest-path> && specfuse init --no-self-upgrade <guest-path> (README: specfuse init /path/to/your-project)","python3 .specfuse/scripts/lint_plan.py .specfuse/features/FEAT-2026-0001-health-endpoint (README: Self-demonstrating reference installation)","specfuse-lint .specfuse/features/FEAT-2026-0001-health-endpoint (flat alias, same check)"],"deviations":["specfuse init refused a non-existent target ('is not a directory'); created the empty directory first, then init succeeded.","specfuse run --dry-run and python .specfuse/scripts/loop.py --dry-run exit 1 with 'No active feature. Set a feature's PLAN.md status to active'. This is the product's guard for a repo without an active feature; I did not edit PLAN.md. Not counted as a failure of the lint operation.","Lint emits WARN lines (missing produces:, planned_cost_usd, legacy 4-WU closing sequence) but reports OK and exits 0.","Git pin not applied: the workspace has no .git and the task's operation does not need git metadata.","No cycle/scheduler detected; no browser needed; no credentials needed."],"stuck_step":null,"main_blocker":null,"plain_failure":null,"suggested_fix":"None for the tested operation. To exercise the driver, a feature would need PLAN.md status set to active by the user, plus the claude CLI for dispatch."}
EOF
python3 -c "import json;json.load(open('report.json'));print('report ok')"; cd <guest-path> && <env-var>=<guest-path> python3 -I <guest-path> --validate --replay 2>&1 | tail -40; echo "rc=${PIPESTATUS[0]}"