Skip to content

ci: remove internal tracking names from public workflow comments and fixtures - #175

Merged
luisleo526 merged 3 commits into
mainfrom
ci-public-token-sweep-0247
Nov 7, 2026
Merged

luisleo526 merged 3 commits into
mainfrom
ci-public-token-sweep-0247

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

Summary

Removes internal tracking names from public workflow comments and fixtures. Each workflow comment changes together with its pinned canon copy and the test literal that checks it, so the canon pins stay consistent. Behaviour is unchanged.

Tests

The workflow policy tests pass on this head; the parent fails the token check that guards against these names, as expected.

🤖 Generated with Claude Code

Keep workflow comments, canon copies and policy-test literals in sync.
Keep the byte-review gate bound to the edited workflow definitions.
Keep SOURCE metadata hashes aligned with the edited canon fixtures.

@graphify-labs graphify-labs Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Graphify reviewed this change.

No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.

Not checked: tests were not run; no formal proof of the changed code.


Graphify review — findings

Strips internal ticket references (LB-437, LB-570, #1050/#1051) from comments in the CI workflows, the canon fixtures, and the PR-tier workflow tests, leaving the shell logic unchanged. Because the release-chain evidence check pins SHA256 hashes of the reviewed ci.yml and ci-post.yml, this updates REVIEWED_CI_WORKFLOW_SHA256 and REVIEWED_CI_POST_WORKFLOW_SHA256, plus the fixture checksums in SOURCE.txt, to match the edited files. The canonical authz script string in test_pr_tier_workflows.py gets the same comment edit so the exact-match assertions still line up.

No blocking issues surfaced.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 208 functions depend on the 157 functions this change touches.

Health — grade B; 10 existing hotspot(s) in the area this change touches (pre-existing, not introduced here):

  • reconcile() — 8 callers, 26 callees (high)
  • publication() — 4 callers, 18 callees (high)
  • candidate_gate() — 13 callers, 5 callees (high)
  • maybe_merge() — 3 callers, 18 callees (high)
  • recover_applied() — 4 callers, 13 callees (high)
  • create_evidence() — 7 callers, 7 callees (high)
  • gate_for_run() — 8 callers, 6 callees (high)
  • prepare() — 2 callers, 17 callees (high)
  • …and 2 more

Verification — 208 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

  • verification_scope: 208 function(s) in the blast radius were not formally verified this run

@luisleo526
luisleo526 merged commit 58c6de4 into main Nov 7, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant