Conversation
…ry (8.32/10) First run covering the most recent release (v1.6.1, develop @ b763d2f). Adds: - docs/repowise/history.md — NEW cross-run trend log (now 4 rows); auto-appended each run by generate-report.py; idempotent per commit - docs/repowise/health.md + per-module reports — regenerated from THIS run's scoped JSON (988→1017 files, 8.26→8.32) - .sc/repowise/generate-report.py — load_json hardened (repowise CLI now emits log-line prefixes in JSON output) - refreshed scoped data: health (compose+composer), dead-code, refactoring-targets Trend: 7.90 (v1.2.0 era) -> 8.23 (v1.6.0-1) -> 8.26 (v1.6.0-15, post Phase-S) -> 8.32 (v1.6.1-10, this run). +0.42 over ~1 month.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sc-compose code health — post-v1.6.1 run (8.32/10)
First run covering the most recent release (v1.6.1, 2026-08-31).
Base:
develop@b763d2ff(= v1.6.1 + 10 commits: Phase-S merge #596, ARM64/release-preflight #595–#602, homebrew fix #603).What lands
docs/repowise/history.md(NEW) — the cross-run trend tracker this repo was missing. One row per run, chronological, auto-appended (idempotent) by the generator. Now 4 rows: 7.90 → 8.23 → 8.26 → 8.32.docs/repowise/health.md+ per-module reports — regenerated from this run's scoped JSON (data in.sc/repowise/data/, committed), so the human-readable files finally match the data..sc/repowise/generate-report.py—load_jsonhardened; repowise now emits log-line prefixes in JSON output, which the old parser rejected.This run
.sc/repowise.yaml)Worst files this run: full-index floor is
.github/scripts/release_artifacts.py(1.90/10); the in-scope floor iscrates/sc-compose/src/commands/template_lint.rs(2.58/10, CCN 9, 576 loc).Phase-S effect (measurable):
crates/sc-composer/src/extract/yaml.rs— the old floor at 2.54 (v1.6.0-1 and v1.6.0-15) — is now 4.70 after the remediation sprints.template_lint.rsis the new in-scope floor.Scope caveat (read before trusting a single number)
repowise health --kpisscans the full repo index (1017 files), while the scored tables restrict to the two configured modules (207 files, ~20% of the index). The two "worst file" values above come from the two different scopes —health.md→ "Quick Summary" carries both with a plain-English note.Verification
repowise update --provider codex_cli --yes— clean exitrepowise health(compose + composer),repowise dead-code,repowise health --refactoring-targets— all exit 0, JSON validgenerate-report.py→OK combined 207 unique files, avg 8.32, files below 3.0: 1;history.mdgrows to 4 rows; trend line reads "+0.06/10 improved"Closes the "no run after v1.6.1" gap. Supersedes the #571/#581 data runs (their bases predate v1.6.1).