[Promote] ci: keep develop Web CI required contexts reportable (#229)

[github-actions]

Automated promotion of #229 from develop to main, opened by the Promote features to main workflow for release review.

Source

Source PR	#229 — ci: keep develop Web CI required contexts reportable
Author	@lopugit
Merged into develop	2026-08-10T08:34:06Z
Merge commit	c145673b6f621efc9ec857d27d9de5e7f88666df
Head branch	codex/web-ci-required-context-develop

⚠️ Source-lineage review required

Do not merge this promotion unless restoring the historical source change is intended.

Later edits overlap the historical patch, so its effect cannot be proven present at current develop tip.

The workflow recovered and re-applied source PR #229's exact historical patch deterministically. A model-authored release analysis is posted as a comment on this promotion: it examines main, develop, and github-actions history plus the PR inventory, infers whether this change still belongs, and names any base-only work the replay would override (with recommended follow-up PRs). It is advisory — the replay content itself never comes from a model.
A reviewer must compare this candidate with current product intent before merging it to main.

Lineage status: review-required-ambiguous · current source tip was checked automatically.

How to review

• This PR re-applies the source PR's exact changes onto main
  (the trusted worker reconstructs one exact bot-authored synthetic commit).
• Merge it normally to release the change to main —
  the Sync main into develop workflow keeps develop aligned afterwards.
• Close it (without merging) to keep the change out of main;
  the workflow never recreates a closed promotion (reopen it to change your mind).
• Prefer shipping everything at once? Merge the standing omnibus
  Promote develop to main PR instead — this PR's diff then becomes
  empty and the workflow closes it automatically.

Protected clean-replay review

• This candidate was quarantined before the promoter applied any historical commit because the exact source patch changes CI-sensitive .github/** content and its source lineage is review-required-ambiguous.
• The trusted worker reconstructs the exact patch as a bot-authored synthetic commit instead of
  publishing original commit messages or executable workflow history with the promotion PAT.
• CI-sensitive content commits are stamped [skip ci]; the bot-authored empty checkpoint
  exposes approval-required PR checks only after the review branch and PR exist.
• A github-actions[bot] comment on source PR ci: keep develop Web CI required contexts reportable #229 attests the exact
  source endpoints, destination base, reservation, plan hash, and published head.
• Please review the exact candidate before merging; no manual branch repair is required.

---

🤖 Generated by the promote-features-to-main workflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
thingtime	Ready	Preview	Aug 18, 2026 4:52am

[github-actions]

🤖 Automatic promotion conflict resolution completed.

Source PR: #229 · plan: 98c77dcefab3eb07bf6f66bce576134b23f1be71cf2fa52d9e7047ba036f7a7f · workflow run

Base: main at c77017cd3a392bdf79f836a403328a7c2d2f6d0d

Reservation: ce3a034e4f0101eda81b9ee8db7970bfe3a8bba4 · verified head: 9f11305cd920174842a185af5eec6e1c94766753

⚠️ Historical source lineage requires an explicit release decision.

The exact source patch was recovered and mechanically verified, but current develop does not prove that it remains intended (review-required-ambiguous). This can represent an intentional revert/removal or overlapping later development. Merge this promotion only if restoring that historical feature is desired.

Under the never-cancel policy this candidate is published for an explicit human decision instead of being dropped; its content commits are review-gated and nothing merges automatically.

Please manually review the paths the isolated AI resolved:

• .github/workflows/web-ci.yml
• TESTING.md
• remix/CHANGELOG.md
• remix/package.json
• remix/scripts/web-ci-required-context-contract.mjs

Model waterfall: --model claude-opus-5 --fallback-model claude-fable-5,default · Graphify refresh: true (semantic: claude-cli).

⚠️ This promotion resolves CI-sensitive .github/** files. Its content commits are stamped [skip ci]; the final empty non-skip checkpoint creates approval-required PR checks without executing AI-edited push workflows.
Approve those checks only after reviewing the paths above.
External preview/webhook integrations should also be reviewed before relying on any deployment from this branch.

[github-actions]

🤖 Auto-resolve running — the conflict resolver started working on this PR at 05:59 UTC.

Expected to finish around 06:07 UTC (most resolutions still land in 3-8 minutes; the hosted-runner ceiling is 360). On success a merge commit resolving the conflicts is pushed to this branch and a result comment follows — no manual action is needed meanwhile.

Live status

[github-actions]

🤝 Merged main into promote/pr-229-web-ci-required-context-develop--to-main — conflicts auto-resolved by the resolve-pr-conflicts workflow.

Conflicted files:

• remix/CHANGELOG.md
• remix/package.json

Please review the merge commit before relying on it.

[github-actions]

⚠️ The resolver stopped in a later safety, verification, or publication step. No residual conflicted paths were confirmed; see the workflow run.

[github-actions]

🤝 Merged main into promote/pr-229-web-ci-required-context-develop--to-main — conflicts auto-resolved by the resolve-pr-conflicts workflow.

Conflicted files:

• graphify-out/GRAPH_REPORT.md
• graphify-out/graph.json
• graphify-out/manifest.json
• remix/package.json

graphify-out/ was reset wholesale to the main side (repo rule: one side, never mixed — the graph merge driver is unavailable in CI).
Then re-ran graphify on the merged code WITH LLM semantic extraction (graphify extract, claude-cli backend) and committed the result — content new to this merge is semantically indexed; unchanged content came from the tracked cache.

Please review the merge commit before relying on it.

[github-actions]

⚠️ The resolver stopped in a later safety, verification, or publication step. No residual conflicted paths were confirmed; see the workflow run.

[github-actions]

🤝 Merged main into promote/pr-229-web-ci-required-context-develop--to-main — conflicts auto-resolved by the resolve-pr-conflicts workflow.

Conflicted files:

• graphify-out/GRAPH_REPORT.md
• graphify-out/cache/semantic/c73683e4552322d9eed2385637ca3b22ca169ea3559acd1287868fc45be1fa52.json
• graphify-out/graph.json
• graphify-out/manifest.json
• remix/CHANGELOG.md
• remix/scripts/workflow-caller-contract.mjs

graphify-out/ was reset wholesale to the main side (repo rule: one side, never mixed — the graph merge driver is unavailable in CI).
Then re-ran graphify on the merged code WITH LLM semantic extraction (graphify extract, claude-cli backend) and committed the result — content new to this merge is semantically indexed; unchanged content came from the tracked cache.

Please review the merge commit before relying on it.

[github-actions]

⚠️ Could not auto-resolve every conflict with main — manual resolution is needed for the residual paths below. See the workflow run.

Residual conflicted files:

• remix/CHANGELOG.md
• remix/package.json

Automatic retries are paused with ai-merge-paused so the scheduled sweep cannot repeat the same failed AI run forever. After review, run this action manually with PR 277 (or its exact base/head branch) to clear the hold and retry.

[github-actions]

⚠️ The resolver stopped in a later safety, verification, or publication step. No residual conflicted paths were confirmed; see the workflow run.

[github-actions]

🤝 Merged main into promote/pr-229-web-ci-required-context-develop--to-main — conflicts auto-resolved by the resolve-pr-conflicts workflow.

Conflicted files:

• .github/workflows/web-ci.yml
• graphify-out/GRAPH_REPORT.md
• graphify-out/cache/semantic/063fea719e6b0e584466a3c5db4819e59688a92bac86df7be07c75a96d8b6a2a.json
• graphify-out/cache/semantic/6fb1b49cbb9aeac1e845084c9b62ca3421faae065316d5b6bf4a54fa8ad4fe50.json
• graphify-out/cache/semantic/8a45daca4b7ad00f3f629ee2c2358fcfa2e3d2a3e9cc9af389d1c4f0a31da3f9.json
• graphify-out/cache/semantic/ab5050911111a908aaf14b88043cc6f48ace435518b325062e728c1a22267461.json
• graphify-out/cache/semantic/b72c0b5bfbc6a13338a54cbeb0197715411e8d71d4021d5e53e2d4a565d205bc.json
• graphify-out/cache/semantic/c4d90b648c3b7e1d2f9f5b3fabbd8999abf03f2e3bce2989672675eae96f380f.json
• graphify-out/cache/semantic/e22056684b94654f2037143b00a0e5fb21cb25a236fbc9f051f81bcdefdd1c98.json
• graphify-out/cache/semantic/ed02febbafa104fb4fb635601c99b70ce7cb4099aae665254bdf8946119f50a5.json
• graphify-out/graph.json
• graphify-out/manifest.json
• remix/CHANGELOG.md
• remix/package.json

graphify-out/ was reset wholesale to the main side (repo rule: one side, never mixed — the graph merge driver is unavailable in CI).
Then re-ran graphify on the merged code WITH LLM semantic extraction (graphify extract, claude-cli backend) and committed the result — content new to this merge is semantically indexed; unchanged content came from the tracked cache.

Please review the merge commit before relying on it.