Repository navigation
Release/v1.5.0 - #30
Merged
Merged
Conversation
Keep the parser fuzz generator total after repeated truncation by clamping byte-flip positions to the shortened binary. Add the exact StreamData counterexample from CI as a deterministic regression test and document the test-harness correction in the 1.4.5 changelog.
Resolve registered fonts and default fonts consistently for wrapping, alignment and drawing. Honor design tokens and inline italic/oblique styles, and draw configurable underline and strikethrough decorations.
Introduce Page.clip and compile balanced graphics-state clipping operations for both page and local content. Transform clip paths according to the page origin so rounded and circular image crops remain correctly positioned.
Add containers, rows, columns, arbitrary block grids, overlays, vector shapes/icons, badges, linked buttons and framed images. Cache measured child placements, align unequal cells, preserve nested navigation, and reject overflowing atomic compositions. Wire native Flow and declarative APIs with regression coverage for fonts, clipping, links, nesting and pagination.
Provide a four-page .paperforge gallery showing composition, alignment, clipping, overlay QR, mixed typography, tables and charts. Document options and atomic pagination limits, package the guide, and add independent pypdf structural verification.
Add warmed, repeated small/QR/visual rendering scenarios at multiple concurrency levels. Retain baseline, exploratory and final samples; report medians and sampled memory, including the default QR regression at four workers rather than claiming universal speedups.
Add autonomous orchestration, OS/thermal sampling, frozen-core checks, finalization and summary generation. Extend render profiles and concurrent scenarios for latency, scheduler scaling and sustained throughput; keep workload setup outside timed rendering.
Document token/theme precedence, canonical fingerprint migration, navigation/endnote behavior, QR configuration and visual primitives. Record verification outcomes and concurrent measurement limitations for the 1.5.0 review.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Preserve the completed 2026-10-26 campaign evidence for this workload/scheduler configuration, including render samples and available OS/thermal observations. These are historical measurements of the frozen core identified in environment.md, not measurements of the later tuning changes. Split large raw datasets into bounded commits without modifying their contents.
Archive the completed campaign report, CSV summaries, validation results, exact source snapshot and environment identity. Retain raw-run provenance so reported throughput and sustained measurements can be audited against the original workload.
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.
No description provided.