Skip to content

test(diagrams): pin exact SVG fixture output (FU-1015) - #1833

Merged
mergify[bot] merged 1 commit into
mainfrom
codex/fu1015-svg-exact
Oct 22, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
codex/fu1015-svg-exact

Conversation

@Cuarroc

@Cuarroc Cuarroc commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Der Test prüft jetzt die vollständige SVG-Ausgabe der vorhandenen kleinen Vorlage. Dadurch fallen auch Änderungen auf, die die bisherigen Einzelprüfungen nicht erkennen. Für dich ist nichts zu tun; Prüfung und Abnahme folgen durch die Koordination.

Report

Plan-ID: FU-1015

Package: FU-1015 / R1581-K3 (parent PR #1581) · Review tier: C, test-only.
Goal / benefit: Close the missing exact-output coverage with an independent literal expected SVG, exercised through the exporter's public CLI.
Parent / ticket / owner: FU-1015; ticket 2c8ddf2f-60fe-414c-b6e0-6d038a04ba5f; job86 / srv-fu1015-svg-exact. Root owns acceptance and subsequent integration.
Base: 88c10c7716ad2dca629930adbcd8a291baf5d858 · Head: efd6c03aeb352303c823283af3f1fe5d7834a5a3 · Branch: codex/fu1015-svg-exact · Raw diff: 10 added, 0 deleted lines, one file.

What changed

Extend the existing light-theme fixture test in docs/diagrams/export-svg.test.mjs with complete string equality. The literal pins the 12/12/176/116 crop, accessibility metadata, background, node geometry and paint, inline text styles, tspan whitespace and serialization. The expected string is written literally from the small fixture and its contract; it is not calculated by the exporter or strip helper. The existing focused assertions remain intact. No exporter, strip implementation, renderer, fixture, diagram, snapshot, dependency or CI file changes.

No-Test rationale: This is missing test coverage for already-correct behavior. The existing fixture suite passed before and after the assertion; no product bug or artificial failing test is claimed. The commit carries a justified No-Test: trailer.

Evidence

Observed on 2026-10-22 in this branch's own worktree; all post-commit checks bind to the head above.

Command Exit code / observation
npm run dev:start-check -- --max-cargo 4 --min-free-gb 3.5 0 before implementation, commit, full prepush and push; separate admission checks confirmed available memory >=3500 MiB and load1 <12
node --test docs/diagrams/export-svg.test.mjs 0 before and after; 6 passed, 0 skipped; Chromium actually ran
bash scripts/ci/secret-scan.sh 0 before commit; no leaks
git commit with normal hooks 0; full precommit lane passed
bash scripts/ci/red-first.sh 0; justified No-Test / test-only change, no bug RED claimed
bash scripts/ci/gates.sh lane prepush 0 at the stated head; 1707 frontend tests and 2320 Rust tests passed; SVG export gate passed
git push -u origin codex/fu1015-svg-exact 0; normal prepush hook also ran the full lane and passed
git ls-remote origin codex/fu1015-svg-exact 0; remote head equals efd6c03aeb352303c823283af3f1fe5d7834a5a3
git diff --check 88c10c7716ad2dca629930adbcd8a291baf5d858 HEAD 0

Native evidence: Own get_goal returned no goal, then create_goal created the bounded ticket goal; subsequent get_goal confirmed it active. The worker goal ends at checked draft handover, not parent acceptance. Actual session turn_context reported gpt-6.1-sol, effort high, provider openai; subscription authentication was observed. Exact process/session/admission evidence stays in the private worker handover.
Source coverage: Read the fixture, exporter and strip helper directly. No native graph or AgentsRoom memory tool was available, and the local lage-jetzt mirror was absent; no graph-completeness claim. Live PR/branch checks were used.

NICHT ABGEDECKT

  • Linux does not compile or run #[cfg(windows)] tests (including ConPTY, DPAPI and npm shim paths) or Windows clippy branches. The Windows lane remains for the merge queue.
  • Existing suite exclusions remain: 7 Rust tests skipped, 3 HQ Node cases skipped (two Windows wrappers and a symlink-output subcase), and 1 Windows 8.3 Denkraum case skipped. No skips were added or assertions weakened here; all 6 SVG tests ran.
  • The exact literal covers this existing light-theme fixture. It is not evidence of dark-theme correctness or every possible SVG input/browser/font environment.
  • No screenshot inspection, visual-quality claim, real desktop app run, frontend production build, standalone Linux CI lane, or external-service verification.
  • The offline plan gate does not verify live PR status or running assignments.

Reviews and disposition

Review: ausstehend (Stufe C). Root commissions any reviews and owns acceptance, ready status, labels and Mergify. This worker did not review, queue or merge the change.

Open points / handover

Implemented, locally tested, committed and remotely verified; submitted as draft. Root's review/acceptance and merge-queue Windows evidence remain open. The frozen canonical FU-1015 row still has its dated generic dispatch status; this file-only assignment does not edit PLAN, so orchestration status reconciliation remains with Root. No scope adaptation or product behavior change.

Pin the existing light-theme fixture output with an independent literal.\nCover the exact crop, metadata, paint, geometry and text whitespace while\nretaining the existing focused assertions.

No-Test: Test-only missing coverage for already-correct export; baseline and candidate fixture tests pass, so no artificial bug RED.

Co-Authored-By: GPT-6.1 <noreply@openai.com>
@Cuarroc
Cuarroc marked this pull request as ready for review October 22, 2026 12:22
@Cuarroc Cuarroc added the review-ok Pipeline: review disposition complete, no open high finding label Oct 22, 2026
@Cuarroc

Cuarroc commented Oct 22, 2026

Copy link
Copy Markdown
Owner Author

Root acceptance (tier C, test-only: docs/diagrams/export-svg.test.mjs +10/-0): diff read, independent literal expected SVG through the public CLI; prepush 0 and ls-remote match per report, own ls-remote 12:23Z = efd6c03. review-ok bound to head efd6c03; any later push voids it. Queue follows when checks are green.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-22T12:24:47.134467Z efd6c03 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: efd6c03aeb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

+ '<tspan style="fill:#000000;font-family:Geist, Inter, -apple-system, BlinkMacSystemFont, \'Segoe UI\', sans-serif;font-size:16px;font-weight:400;text-anchor:start">Hello</tspan> '
+ '<tspan style="fill:#000000;font-family:Geist, Inter, -apple-system, BlinkMacSystemFont, \'Segoe UI\', sans-serif;font-size:16px;font-weight:400;text-anchor:start">World</tspan>'
+ '</text></g></svg>';
assert.equal(svg, expected);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Reconcile FU-1015 in the canonical plan

This assertion completes the R1581-K3 follow-up, but at the reviewed head docs/PLAN.md:365 still describes all FU-1015 items as “Geplant: nicht disponiert” and does not record this dispatched, implemented package. Update or split that row in this change so the canonical plan states the post-merge status rather than deliberately leaving reconciliation to Root afterward.

AGENTS.md reference: AGENTS.md:L139-L139

Useful? React with 👍 / 👎.

@Cuarroc

Cuarroc commented Oct 22, 2026

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify

mergify Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

queue

☑️ This pull request is already queued

@mergify mergify Bot added the queued label Oct 22, 2026
@mergify mergify Bot mentioned this pull request Oct 22, 2026
30 of 46 tasks
@mergify
mergify Bot merged commit 72ae3f7 into main Oct 22, 2026
25 checks passed
@mergify

mergify Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-10-22 12:30 UTC · Rule: default · triggered by merge protections
  • ✅ Checks passed · on draft merge queue: checking #1833 on main (88c10c7) #1834
  • ✅ Merged — 2026-10-22 13:05 UTC · at 72ae3f7582f2c5e877f0d76d281856e28c563369 · merge

This pull request spent 35 minutes 47 seconds in the queue, including 35 minutes 15 seconds running CI.

Required conditions to merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-ok Pipeline: review disposition complete, no open high finding

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant