feat(st4): contributor funnel + foreign-harness inspect adapter + 0.8.0 release cut - #33
Conversation
…r + vendored fixture
…records + non-null RP
…RIBUTING start-here section
…mplates/recipes, not a good first issue
…ommit note and PR-A review
…loud guard Whole-branch review (Important, confirmed): README said 'no installs' but run-example shells the real gate whose probes need pytest; on stdlib-only python3 it died silently (set -e, exit 1, zero output) after clobbering the tracked verdict fixture. README now names the pytest requirement; the script checks for pytest up front and prints the uv one-liner before touching anything.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9bc198d6fc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if _newest_md(ws / _SPECS_DIR) or _newest_md(ws / _PLANS_DIR): | ||
| return "superpowers" |
There was a problem hiding this comment.
When a non-foreign project contains docs/superpowers/specs or docs/superpowers/plans for its own documentation but has not emitted .loop/state.json (the repo root here is such a case), this condition maps the whole workspace as a Superpowers run. I checked python3 -m loop inspect . in this checkout: it now reports foreign_layout: "superpowers" and an ok-level score by combining those docs with the repo's normal scripts, instead of reporting the missing native contract. Please require a stronger foreign-run marker, such as the .superpowers/sdd journal plus a matching spec/plan, before returning superpowers.
Useful? React with 👍 / 👎.
feat(st4): contributor funnel + foreign-harness inspect adapter + 0.8.0 release cut
Second half of v0.8.0 "composes-the-field" (spec:
docs/superpowers/specs/2026-07-08-v0.8.0-composes-the-field-design.md; plan:docs/superpowers/plans/2026-07-08-v0.8.0-composes-the-field.md). PR-A (ST3 adapters + recipes) merged as #32.Deliverables
loop/foreign.py, a read-only layout mapper that letsloop inspectrecognize a Superpowers-style run dir via the existingLoopPathsseam. The M2/M3-hardened scorer is untouched; a foreign harness with no gate and no terminal record scores honestly low (no-invoked-credit regression test binds). Vendored, sanitized fixture atexamples/superpowers-run/.docs/gap-reports/superpowers.md: the §14 conformance checklist read against the vendored fixture; every claim fixture-checkable; complement-not-attack framing.examples/flaky-test-triage/: doctor-clean, gate-backed, the showcase for repair records —loop metricsderives a non-null repair-productivity of 1.0 from its anchored red→green repair (FCR 0.0).docs/contributing/issues/(3good first issue+ 4help wanted, filed live at merge) + CONTRIBUTING start-here section.Acceptance criteria (spec §5, PR-B items)
python3 -m loop inspect <foreign-dir>produces a scored report against the vendored fixture; gap report checked in; 2nd example passesdoctorself_eval.py,validate_frontmatter.py,py_compile; CI green incl. both recipe jobstest_docs_versionpins itTest plan
uv run --with pytest --with pyyaml --with jsonschema python -B -m pytest -q -p no:cacheprovider scriptsvalidate_frontmatter.py(9/9),self_eval.py(13/13),py_compile,loop doctor examples/flaky-test-triage,loop inspect examples/coverage-repair(90/strong unchanged)loop metrics examples/flaky-test-triage→ FCR 0.0, RP 1.0, no unrecognized outcomes;loop inspect examples/superpowers-runmatches the gap report §4 JSONNotes for reviewers
manifest.yaml/WORKFLOW.mdfollow the flagship-example precedent; example scripts are invoked asbash <script>so 100644 mode is fine.v0.7.0@ 4647820 andv0.8.0@ the release commit.