chore: align commit-message workflow #14

Merged
jercik merged 1 commit from chore/align-runtime-15-2-5 into main 2026-10-25 10:03:31 +00:00
Owner

Synchronizes the commit-message workflow with released Align 15.2.5.

Synchronizes the commit-message workflow with released Align 15.2.5.
chore: align commit-message workflow
All checks were successful
Checks / pr-flow-canary (pull_request) Has been skipped
commit-msg / commitlint (pull_request) Successful in 5s
Checks / reuse (pull_request) Successful in 7s
Checks / quality-checks (24.15.0) (pull_request) Successful in 33s
Checks / quality-checks (26.12.1) (pull_request) Successful in 41s
Review / Review (pull_request_target) Successful in 6m18s
351d742451

Review 01M5S7985VRNZMFFNA3RDWYN1D — head 351d742451e4658b6a3bd052bb0459b9fa842375

Review — j4k-oss/fta-check @ 08bef757a0

Scope: diff against base tree 7fec3b4ec8a3
Review finished: 4 succeeded, 0 failed, 6 skipped by dispatch
Triage: settled
Facts: current review-wide projection

Computed under:

{
  "abandonment": "abandonment-v1",
  "anchor_recipe": 1,
  "batch_policy": "batch-v1",
  "coverage": "coverage-v3",
  "dispatch_policy": "dispatch-v2",
  "grounder_version": 1,
  "grounding_read_rule": "grounding-read-v1",
  "promotion_policy": "promotion-v1",
  "report": "report-v5",
  "tally": "tally-v1",
  "triage_settle": "triage-settle-v2"
}

Findings (0)

No findings survived.

Reviewed:

  • restated-sets (whole/default): no-claims
  • module-design (whole/default): no-claims
  • aposd-plain (whole/default): claims-emitted
  • general-bug (whole/default): no-claims
  • writing-quality: skipped-by-dispatch — only a workflow step removal; no prose changed
  • test-trimming: skipped-by-dispatch — no tests changed
  • project-docs: skipped-by-dispatch — no documentation changed
  • unix-cli: skipped-by-dispatch — no CLI behavior changed
  • use-effect: skipped-by-dispatch — CI workflow YAML only; no React code
  • react: skipped-by-dispatch — CI workflow YAML only; no React code

Other claims

  • grounding-pending (0)
  • ungrounded (0)
  • rejected (0)
  • duplicate-of (0)
  • unadjudicated (1)
    • 01M5S7EBKXTMKQJXQB13HZJGQJ medium — commit-msg job still runs its PR-metadata parser with node -e but no longer provisions Node, so the gate depends on whatever runtime the runner image has

Coverage

Coverage pass: 01M5S79JGA2023CG6X5SE4HZ12
Accounting: complete (all slots terminal; see slot results for failures)
Slot health: healthy

lens part arm unit status runs loss
restated-sets whole default no-claims 1 no
module-design whole default no-claims 1 no
aposd-plain whole default claims-emitted 1 no
general-bug whole default no-claims 1 no
  • writing-quality — skipped-by-dispatch: only a workflow step removal; no prose changed
  • test-trimming — skipped-by-dispatch: no tests changed
  • project-docs — skipped-by-dispatch: no documentation changed
  • unix-cli — skipped-by-dispatch: no CLI behavior changed
  • use-effect — skipped-by-dispatch: CI workflow YAML only; no React code
  • react — skipped-by-dispatch: CI workflow YAML only; no React code
<!-- review:summary --> **Review** `01M5S7985VRNZMFFNA3RDWYN1D` — head `351d742451e4658b6a3bd052bb0459b9fa842375` # Review — j4k-oss/fta-check @ 08bef757a0d8 Scope: diff against base tree `7fec3b4ec8a3` Review finished: 4 succeeded, 0 failed, 6 skipped by dispatch Triage: settled Facts: current review-wide projection Computed under: ```json { "abandonment": "abandonment-v1", "anchor_recipe": 1, "batch_policy": "batch-v1", "coverage": "coverage-v3", "dispatch_policy": "dispatch-v2", "grounder_version": 1, "grounding_read_rule": "grounding-read-v1", "promotion_policy": "promotion-v1", "report": "report-v5", "tally": "tally-v1", "triage_settle": "triage-settle-v2" } ``` ## Findings (0) No findings survived. Reviewed: - restated-sets (whole/default): no-claims - module-design (whole/default): no-claims - aposd-plain (whole/default): claims-emitted - general-bug (whole/default): no-claims - writing-quality: skipped-by-dispatch — only a workflow step removal; no prose changed - test-trimming: skipped-by-dispatch — no tests changed - project-docs: skipped-by-dispatch — no documentation changed - unix-cli: skipped-by-dispatch — no CLI behavior changed - use-effect: skipped-by-dispatch — CI workflow YAML only; no React code - react: skipped-by-dispatch — CI workflow YAML only; no React code ## Other claims - grounding-pending (0) - ungrounded (0) - rejected (0) - duplicate-of (0) - unadjudicated (1) - `01M5S7EBKXTMKQJXQB13HZJGQJ` medium — commit-msg job still runs its PR-metadata parser with `node -e` but no longer provisions Node, so the gate depends on whatever runtime the runner image has ## Coverage Coverage pass: 01M5S79JGA2023CG6X5SE4HZ12 Accounting: complete (all slots terminal; see slot results for failures) Slot health: healthy | lens | part | arm | unit status | runs | loss | | --- | --- | --- | --- | --- | --- | | restated-sets | whole | default | no-claims | 1 | no | | module-design | whole | default | no-claims | 1 | no | | aposd-plain | whole | default | claims-emitted | 1 | no | | general-bug | whole | default | no-claims | 1 | no | - writing-quality — skipped-by-dispatch: only a workflow step removal; no prose changed - test-trimming — skipped-by-dispatch: no tests changed - project-docs — skipped-by-dispatch: no documentation changed - unix-cli — skipped-by-dispatch: no CLI behavior changed - use-effect — skipped-by-dispatch: CI workflow YAML only; no React code - react — skipped-by-dispatch: CI workflow YAML only; no React code
Author
Owner

Review outcome for unadjudicated claim 01M5S7EBKXTMKQJXQB13HZJGQJ (medium) at 351d742451e4658b6a3bd052bb0459b9fa842375: the parser uses the runner image’s Node, as the current released contract explicitly requires. Align #847, commit 8c1d7391b4b364c55fd454cacbf3fb97bb052c3a, intentionally removed setup-node and documented that runtime ownership. I inspected that source and the SRI-verified 15.2.5 template; this PR adopts those exact managed bytes. The real current-head commit-message job passed its metadata parser and title/subject checks. No missing interpreter or incompatible behavior is demonstrated. Restoring a consumer-specific pin would reverse the released shared decision, so this claim requires no source change or follow-up.

Review outcome for unadjudicated claim `01M5S7EBKXTMKQJXQB13HZJGQJ` (medium) at `351d742451e4658b6a3bd052bb0459b9fa842375`: the parser uses the runner image’s Node, as the current released contract explicitly requires. [Align #847](https://code.j4k.dev/j4k/align/pulls/847), commit `8c1d7391b4b364c55fd454cacbf3fb97bb052c3a`, intentionally removed setup-node and [documented that runtime ownership](https://code.j4k.dev/j4k/align/src/commit/8c1d7391b4b364c55fd454cacbf3fb97bb052c3a/docs/managed-workflows.md). I inspected that source and the SRI-verified 15.2.5 template; this PR adopts those exact managed bytes. The real current-head commit-message job passed its metadata parser and title/subject checks. No missing interpreter or incompatible behavior is demonstrated. Restoring a consumer-specific pin would reverse the released shared decision, so this claim requires no source change or follow-up.
jercik merged commit da5d03720c into main 2026-10-25 10:03:31 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
j4k-oss/fta-check!14
No description provided.