Skip to content

fix(ticket-083): bound large comparison graphs - #100

Merged
ifuri-validator-agent[bot] merged 1 commit into
mainfrom
fix/ticket-083-large-graph-comparison
Aug 25, 2026
Merged

fix(ticket-083): bound large comparison graphs#100
ifuri-validator-agent[bot] merged 1 commit into
mainfrom
fix/ticket-083-large-graph-comparison

Conversation

@tom-sapletta-com

Copy link
Copy Markdown
Contributor

Outcome

  • keeps the generic JSON read ceiling at 128 MiB
  • applies an explicit 256 MiB ceiling only to the two generated workspace-comparison graphs
  • reproduces and passes the 142,557,246-byte graph from Subactor ticket PLF-8091

Evidence

  • npm run verify: 426 tests, 425 pass, 1 JDK-only skip
  • focused workspace suite: 4/4
  • governance: 0 errors, 0 warnings
  • Docker smoke: pass
  • exact Platform replay: exit 0, stderr empty; semantic blocking +2 is now observable

No merge is claimed by this branch; protected exact-head review remains authoritative.

@ifuri-validator-agent ifuri-validator-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Deterministic Validator approval for exact head 810dc8ea75b764a7f3115e2976e181c41fcc2d8b.

Ticket: ticket-083
Correlation ID: todo2code-pr-100-ticket-083-large-graph
Model: zai/glm-5.3
Reviewed diff chunks: 2
Advisory LLM verdict: APPROVE
Advisory summary: Reviewed all 2 diff chunk(s). Adds a comparison-specific 256 MiB ceiling for reading the two generated workspace-comparison graphs while leaving the generic 128 MiB JSON limit unchanged, motivated by a live 142,557,246-byte Platform graph failure. Change is small, scoped to workspace.ts with a regression test, and is well documented across ticket metadata. All checks in test_results_data pass. | Test-only chunk adds a regression test asserting the workspace-comparison graph byte ceiling (256 MiB) exceeds the observed 142,557,246-byte Platform graph. Tests pass in provided logs; no failing checks.
Advisory findings: none
The LLM output above is advisory and was not used as the approval trust root.
Merge will be attempted after this approval when explicitly authorized.

Decision record (recomputable)

DECISION D-083-8885
TICKET ticket-083
HEAD_SHA 810dc8ea75b764a7f3115e2976e181c41fcc2d8b
CORRELATION_ID todo2code-pr-100-ticket-083-large-graph
ACTOR agent:ifuri-validator-agent[bot]
APPLIED_RULE P-CORE-015
INPUT author_login = "tom-sapletta-com"
INPUT observed_checks = ["Live OpenRouter contract (opt-in)=SKIPPING","governance=SKIPPING","Java adapter (JDK 17 required)=PASS","verify=PASS","koru / code-review=PASS","verify=PASS","Java adapter (JDK 17 required)=PASS"]
INPUT required_checks = ["verify","Java adapter (JDK 17 required)","koru / code-review"]
INPUT required_checks_source = "protected registry + GitHub applied rules (env/request)"
INPUT reviewer_login = "ifuri-validator-agent[bot]"
VERDICT APPROVE AUTHORITY DETERMINISTIC
REJECTED REQUEST_CHANGES BECAUSE NO_UNSAFE_CHANGE_REASON_FOUND
ADVISORY llm_verdict = "APPROVE" MODEL "zai/glm-5.3"
ASSERT VERDICT_AUTHORITY != "ADVISORY"

@tom-sapletta-com

Copy link
Copy Markdown
Contributor Author

Closing without merge: hosted implementation tests pass, but protected governance fails because refactor/god-modules-split, ticket-021 and ticket/078-082-ticket-safety are unowned remote branches with unique commits. Their deletion is not authorized and would lose data. The PR branch is preserved for a future governed branch-lifecycle reconciliation.

@ifuri-validator-agent ifuri-validator-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Deterministic Validator approval for exact head 810dc8ea75b764a7f3115e2976e181c41fcc2d8b.

Ticket: ticket-083
Correlation ID: todo2code-pr-100-ticket-083
Model: zai/glm-5.3
Reviewed diff chunks: 2
Advisory LLM verdict: APPROVE
Advisory summary: Reviewed all 2 diff chunk(s). Chunk 1 of 2 adds a comparison-specific 256 MiB read ceiling for the two generated intent graphs while keeping the generic 128 MiB JSON limit unchanged, with regression tests and ticket documentation updates. Code change is minimal, well-commented, and matches the stated intent. | Test chunk adds a bounded graph ceiling regression test asserting WORKSPACE_COMPARISON_GRAPH_MAX_BYTES (256 MiB) exceeds the observed 142,557,246-byte Platform graph. All reported checks pass.
Advisory findings: none
The LLM output above is advisory and was not used as the approval trust root.
Merge will be attempted after this approval when explicitly authorized.

Decision record (recomputable)

DECISION D-083-6264
TICKET ticket-083
HEAD_SHA 810dc8ea75b764a7f3115e2976e181c41fcc2d8b
CORRELATION_ID todo2code-pr-100-ticket-083
ACTOR agent:ifuri-validator-agent[bot]
APPLIED_RULE P-CORE-015
INPUT author_login = "tom-sapletta-com"
INPUT observed_checks = ["governance=SKIPPING","Live OpenRouter contract (opt-in)=SKIPPING","verify=PASS","Java adapter (JDK 17 required)=PASS","koru / code-review=PASS","verify=PASS","Java adapter (JDK 17 required)=PASS","Java adapter (JDK 17 required)=PASS","verify=PASS","koru / code-review=PASS","verify=PASS","Java adapter (JDK 17 required)=PASS"]
INPUT required_checks = ["verify","Java adapter (JDK 17 required)","koru / code-review"]
INPUT required_checks_source = "protected registry + GitHub applied rules (env/request)"
INPUT reviewer_login = "ifuri-validator-agent[bot]"
VERDICT APPROVE AUTHORITY DETERMINISTIC
REJECTED REQUEST_CHANGES BECAUSE NO_UNSAFE_CHANGE_REASON_FOUND
ADVISORY llm_verdict = "APPROVE" MODEL "zai/glm-5.3"
ASSERT VERDICT_AUTHORITY != "ADVISORY"

@ifuri-validator-agent
ifuri-validator-agent Bot merged commit afdbebe into main Aug 25, 2026
21 of 22 checks passed
@ifuri-validator-agent
ifuri-validator-agent Bot deleted the fix/ticket-083-large-graph-comparison branch August 25, 2026 13:14
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