feat(foresight): strengthen portable evidence contract v2

[timerloggedout-spec]

Summary

Advances the merged Foresight Evidence Spine from a structural contract into a continuously exercised interchange layer.

Changes

• adds stable resource_id, item_id, and lane_id identities with backward-compatible normalization
• adds top-level canonical_source and enforces parity with source.url
• records version_or_commit explicitly
• accepts disputed evidence without conflating it with horizon
• adds deterministic lane filtering to the portable radar CLI
• adds a real canonical OpenTelemetry Semantic Conventions evidence record
• expands registry unit coverage
• fixes the workflow to run on master and validate the committed corpus rather than only creating an empty registry
• documents the v2 contract and operational boundary

Validation intent

The branch is 0 commits behind master. CI should verify the unit suite and committed JSONL corpus on the PR SHA.

This is intentionally an interchange-layer slice; it does not replace OpenTelemetry, SQLite, GitHub Actions, or downstream adapters.

[blocksorg]

Mention Blocks like a regular teammate with your question or request:

@blocks review this pull request
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[ecc-tools]

ECC Tools / Security Evidence

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 6 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 6 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

• 1 security-sensitive path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

• API contract changes may ship without integration coverage
• Schema or model changes may ship without migration follow-up
• CI workflow changes may ship without failure-mode evidence
• Dependency or CI drift could surface after merge
• 1 CI or workflow path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml
• foresight/registry.py
• foresight/schema.json
• tests/test_foresight_registry.py

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[vercel]

Deployment failed for project termux-monorepo with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 6 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 6 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Config Audit

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

No changed-config issues detected (success)

Scanned 1 config file(s) present at this commit across 1 changed config path(s) and found no issues in the supported security rules.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[coderabbitai]

Warning

Review limit reached

Next included review available in 36 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: timerloggedout-spec/termux-monorepo/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 3fe427dc-7ec6-4b60-9ebe-9757fb803dfc

📥 Commits

Reviewing files that changed from the base of the PR and between f39fd00 and 75ac41d.

📒 Files selected for processing (6)

• .github/workflows/foresight-evidence-spine.yml
• data/foresight/resource-registry.jsonl
• docs/ops/FORESIGHT-EVIDENCE-SPINE.md
• foresight/registry.py
• foresight/schema.json
• tests/test_foresight_registry.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ecc-tools]

ECC Tools / PR Harness Audit

Commit: 26b654d12713ac390e67e469cabb53461f5f2e18

No harness issues detected (success)

Scanned 1 changed config file(s) and found no harness issues.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[github-actions]

PR Change Effectiveness Ledger

Measured head: 75ac41d5e40cd92ab21aad698a06d16a0525718f
Measured base: f39fd00278246c7cd38232834016e0c6566391ef
Merge base: f39fd00278246c7cd38232834016e0c6566391ef

Signal	Value
commits in PR range	9
commits with no file delta	0
commits with file delta	9
no-op commit rate	0%
gross additions across commits	2233
gross deletions across commits	161
final additions vs base	86
final deletions vs base	113
final changed files	6
churn → retained final diff	8%
ahead / behind base	9 / 0

Interpretation: commit count is context, not quality. Empty commits are explicitly measured, not silently treated as productive work. Gross churn describes work performed across history; the final base→head diff describes what remains. Review/comment/check evidence must be evaluated separately and tied to this measured head SHA.

State: 🟢 EFFECTIVE_DIFF_PRESENT; No empty commits observed.

Generated: 2026-09-27T18:55:55Z

[timerloggedout-spec]

ECC App activity — dual-gate merges; review skills/hooks before merge.

[gitar-bot]

Gitar is working

_Gitar

[ecc-tools]

ECC Tools / Security Evidence

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 6 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[vercel]

Deployment failed for project help-wanted-dash with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 6 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

• 1 security-sensitive path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

• API contract changes may ship without integration coverage
• Schema or model changes may ship without migration follow-up
• CI workflow changes may ship without failure-mode evidence
• Dependency or CI drift could surface after merge
• 1 CI or workflow path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml
• foresight/registry.py
• foresight/schema.json
• tests/test_foresight_registry.py

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[vercel]

Deployment failed for project help-wanted-oversight with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 6 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[vercel]

Deployment failed for project mcp-hub with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 6 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Config Audit

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

No changed-config issues detected (success)

Scanned 1 config file(s) present at this commit across 1 changed config path(s) and found no issues in the supported security rules.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Harness Audit

Commit: e1fc02dc26800744310dff3a604bb929eb195f99

No harness issues detected (success)

Scanned 1 changed config file(s) and found no harness issues.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Security Evidence

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 6 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 6 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

• 1 security-sensitive path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

• API contract changes may ship without integration coverage
• Schema or model changes may ship without migration follow-up
• CI workflow changes may ship without failure-mode evidence
• Dependency or CI drift could surface after merge
• 1 CI or workflow path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml
• foresight/registry.py
• foresight/schema.json
• tests/test_foresight_registry.py

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 6 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 6 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Config Audit

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

No changed-config issues detected (success)

Scanned 1 config file(s) present at this commit across 1 changed config path(s) and found no issues in the supported security rules.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Harness Audit

Commit: 3c3a8061123d628951b232d6b1d7b10cd22414f6

No harness issues detected (success)

Scanned 1 changed config file(s) and found no harness issues.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Security Evidence

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 6 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

PR taxonomy review recommended (neutral)

Detected 2 PR taxonomy bucket(s): Security Evidence, CI/CD Recommendation.

Scanned 6 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

• 1 security-sensitive path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

• API contract changes may ship without integration coverage
• Schema or model changes may ship without migration follow-up
• CI workflow changes may ship without failure-mode evidence
• Dependency or CI drift could surface after merge
• 1 CI or workflow path(s) changed

Paths:

• .github/workflows/foresight-evidence-spine.yml
• foresight/registry.py
• foresight/schema.json
• tests/test_foresight_registry.py

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 6 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 6 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Config Audit

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

No changed-config issues detected (success)

Scanned 1 config file(s) present at this commit across 1 changed config path(s) and found no issues in the supported security rules.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / PR Harness Audit

Commit: 75ac41d5e40cd92ab21aad698a06d16a0525718f

No harness issues detected (success)

Scanned 1 changed config file(s) and found no harness issues.

Changed config files:

• .github/workflows/foresight-evidence-spine.yml

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.