Narrow the chat image so it reads at the same size as the others - #49
Merged
Conversation
The chat session was captured on a 152-column terminal, so its image came out 1052 pixels wide against 791 for every other transcript. Scaled into a documentation page that meant visibly smaller text than the image directly above it, which reads as a broken asset rather than a wide one. Reflowed to 80 columns, matching ask.txt. The prose re-wraps, the two result tables and the SQL box are rebuilt at the narrower width, and the SQL WHERE clause breaks at a clause boundary rather than mid-predicate. The image is now 716 wide and embedded at its natural size, so its text renders at the same scale as ask.svg. Nothing was dropped. Both questions, the follow-up, all four progress lines, both result tables with all nine data rows, the three prose bullets, both command hint lines, the full generated SQL and the exit are present; 43 content assertions and an explicit count of the quarter table's six rows were checked against the reflowed file. What changed is layout, so generate.py now says so. The transcript is reflowed output rather than a byte-exact capture, and a file whose whole job is being evidence should not quietly blur that line. It also records the two things that bite when editing one by hand: box lines within a frame must share a width, and the longest line in the file sets the image width.
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.
The chat session was captured on a 152-column terminal, so its image came out 1052px wide against
791 for every other transcript. Scaled into a page that meant visibly smaller text than the image
directly above it — which reads as a broken asset rather than a wide one.
What changed
Reflowed to 80 columns, matching
ask.txt. The prose re-wraps, both result tables and the SQLbox are rebuilt at the narrower width, and the SQL
WHEREclause now breaks at a clause boundaryrather than mid-predicate. The image is 716px and embedded at its natural size, so its text
renders at the same scale as
ask.svg.Nothing was dropped
Checked rather than assumed — 43 content assertions plus an explicit row count:
/sql /result /exporthint lines/exitlakewright,lakespeak_demo,adb-7405, or the real Agentname
Every box-drawing line is asserted to be exactly 80 characters — the previous version had a
one-character misalignment in the SQL box that I fixed rather than shipped.
The honesty bit
What changed is layout, so
generate.pynow says so. The transcript is reflowed output ratherthan a byte-exact capture, and a file whose whole job is being evidence should not quietly blur
that line. The wording, figures, ordering and command sequence are exactly as the session produced
them; the line breaks are not.
It also records the two things that bite when editing one by hand: box lines within a frame must
share a width, and the longest line in the file sets the image width.
Verification
229 tests green. Regeneration is deterministic. All relative links resolve.