Remove the automatic postprocess failure-policy machine - #11
Merged
tae2089 merged 1 commit intoJul 11, 2026
Merged
Conversation
Postprocess steps (stored-flow + search-index rebuild) run on every build/update; the escalation layer on top of them — auto fail_closed after repeated failures, per-namespace run-log history, and two inspection tools — was operational overhead the project's purpose does not need. Step failures are already visible: they warn to the log and list in the `failed_steps` response field with `status: "degraded"`. - delete internal/postprocess/policy and its two GORM models - add migration 000007 dropping ccg_postprocess_policy_state and ccg_postprocess_run_logs (sqlite + postgres); RequiredSchemaVersion 6 -> 7 - remove get_postprocess_policy and reset_postprocess_policy MCP tools (26 -> 24) - drop the postprocess_policy request arg and fail_closed path; keep the inline degraded behavior (warn + failed_steps) in build_or_update_graph and run_postprocess - remove the PostprocessPolicy Deps field, runtime wiring, HTTP /status postprocess summary, and the `ccg status` postprocess section (+ --errors/--recent flags) - delete guide/postprocess-failure-policy.md (EN + ko) and sweep doc references Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
What
Removes the automatic postprocess failure-policy layer. Postprocess steps (stored-flow + search-index rebuild) still run on every build/update — only the escalation machinery on top of them is deleted: auto
fail_closedafter repeated failures, per-namespace run-log history, and the two inspection tools. Step failures stay visible (warn log +failed_stepsin the response withstatus: "degraded"), so nothing is silently swallowed.Stacked on the analyzer-removal PR — review that first.
Changes
internal/postprocess/policyand its two GORM models.ccg_postprocess_policy_state+ccg_postprocess_run_logs(sqlite + postgres);RequiredSchemaVersion6 → 7.get_postprocess_policyandreset_postprocess_policyMCP tools (26 → 24).postprocess_policyrequest arg and thefail_closedpath; keep inline degraded behavior inbuild_or_update_graph/run_postprocess.PostprocessPolicyDeps field, runtime wiring, HTTP/statuspostprocess summary, and theccg statuspostprocess section (--errors/--recentflags).guide/postprocess-failure-policy.md(EN + ko) and sweep doc references.Verification
go build+go vetclean;go test -tags fts5 ./...green (one pre-existing timing-flaky webhook test,TestStatusHandler_RecentRepos_FailureHasErrorFields, passes in isolation and per-package — unrelated to this change).TestRunMigrations_SqliteDropsPolicyTablesAtHeadasserts both tables are gone at head schema.ccg migrate(schema v7) →ccg build→ ok; no postprocess tables created.tools/listreturns 24 tools;get_postprocess_policy/reset_postprocess_policyabsent; startup logsprompts=4.Stacked on #10.
🤖 Generated with Claude Code