pycforge 1.3.53__tar.gz → 1.3.57__tar.gz

pycforge-1.3.57/CHANGELOG.md

@@ -0,0 +1,1930 @@
+# PyCForge 1.3.57 — Character map
+
+- Add Character Map to Edit, the Python editor context menu and the main toolbar.
+- Compose characters in a transparent single-line field with a focus-colored
+  underline and Copy at its right; browse fourteen compact character groups.
+- Give grid buttons momentary pressed feedback only, with no hover or latched
+  selection appearance. Support mouse, arrow keys, Space and Enter.
+- Keep character-map text in memory; copy only on request. Preserve all file,
+  project, session, converter, clipboard and generated-C behavior.
+
+# PyCForge 1.3.56 — Advanced code clipboard
+
+- Add PyCForge Clipboard to Edit, the Python context menu and the main toolbar.
+- Search copied code, pin and name reusable clips, preview explicit paste
+  transformations, combine clips and inspect Unicode characters.
+- Capture complete Python source bundles with their matching generated C,
+  recording conversion context and preserving historical captures.
+- Keep generated C read-only and project save/session behavior unchanged.
+- Store only explicitly pinned clips in a separate application preference store;
+  ordinary clipboard history stays in memory and typing never opens the dialog.
+
+# PyCForge 1.3.55 — Editor operation progress
+
+- Add a small progress dialog with a reason above its blue bar for large
+  clipboard pastes, lengthy source preparation and generated-C display.
+- Preserve native paste undo, captured clipboard content and multiple cursors;
+  retire pending feedback when its editor or preparation changes.
+- Keep typing, including input-method composition, free of progress dialogs.
+- Retain filesystem, save, project and session code without modification.
+
+# PyCForge 1.3.54 — File badges and menu access
+
+- Distinguish Python, project and C files in directory trees using white page
+  icons with blue grid, eye and C marks, including uppercase extensions.
+- Keep space between the Tools, recent-scan and diagnostics buttons neutral;
+  prevent those clicks from entering the menu bar's spacer action.
+- Give Tools the Alt+O shortcut so it no longer conflicts with Transpile.
+- Add category icons to Help and remove the duplicate logo beside Close.
+- Preserve the file and project save/session behavior introduced in 1.3.53.
+
+# PyCForge 1.3.53 — Saved files and project sessions
+
+- Package Python modules from other folders or drives without moving them;
+  save project bundles at the chosen writable destination.
+- Keep an associated project bundle current when Python saves finish with all
+  modules saved, preserving existing checkpoints and write-conflict checks.
+- Treat saved files reopened at startup as the session's saved baseline;
+  retain save prompts for subsequent edits and failed save attempts.
+- End the project session when the last tab is closed, retire pending file
+  restoration, and preserve saved files, bundles and checkpoints unchanged.
+- Distinguish automatic title-control focus from mouse hover and intentional
+  keyboard focus in recovery dialogs and shared window controls.
+- Update installed Help for these file workflows and preserve the README
+  body and four approved images, with its version heading advanced to 1.3.53.
+
+# PyCForge 1.3.51 — Reliable large-workspace editing
+
+- Avoid repeated text-layout settings during buffer attachment and apply the
+  configured font correctly when returning to an older shared buffer.
+- Release rebuildable inactive large editor buffers under a 32 MiB text-cache
+  target; preserve active text, unsaved edits, undo/redo, previews and return
+  locations. Bound the separate normalized-source cache to 8 MiB.
+- Refuse opens, reloads and project restores that increase retained source and
+  disk-baseline storage beyond 64 MiB, before replacing workspace state.
+  Existing edits, saves, undo/redo and shrinking replacements remain available.
+- Keep retention event-driven, with one coalesced timer and no added worker
+  threads, processes, dependencies or changes to conversion APIs.
+- Explain practical memory limits in HTML Help. Keep the concise README and
+  four approved images; advance the package and README heading to 1.3.51.
+- See PyCForge-1.3.51-Verification.txt and
+  specifications/editor_resources_1_3_51.md for evidence and remaining limits.
+
+# PyCForge 1.3.50 — Responsive large-source loading
+
+- Prepare large source buffers on demand in cancellable GUI steps, with one
+  detached buffer under construction and complete text published atomically.
+- Keep unvisited large companion buffers lazy and preserve completed buffers,
+  edits and undo history across tab switches and split views.
+- Defer source navigation and bundle replacement previews until buffers are
+  ready; retire obsolete work after source, tab or workspace changes.
+- Explain loading behavior, long-line layout limits and memory boundaries in
+  HTML Help. Add one concise README paragraph about API integration contracts;
+  retain the four approved images and advance the version heading.
+- Preserve converter behavior, public API contracts and runtime dependencies.
+- See PyCForge-1.3.50-Verification.txt and
+  specifications/source_loading_1_3_50.md for validation and remaining scope.
+
+# PyCForge 1.3.49 — Faster authenticated workspace revisions
+
+- Scan ordinary source runs in bounded native regex operations, retaining exact
+  Unicode/Qt positions and cooperative cancellation. Dense special-character
+  runs use direct iteration to avoid match-object overhead.
+- Reuse one exact validated source bundle and its existing canonical fingerprints
+  when source, identities, order and conversion settings are unchanged.
+- Share the existing 32 MiB worker cache budget between indexes and bundle facts;
+  clear both on workspace reset/close and remove closed-document source.
+- Preserve independent converter request validation, latest-revision publication,
+  all public API contracts, conversion output and runtime dependencies.
+- Explain revision reuse and API embedding, progress, cancellation and request
+  identity in HTML Help. Keep the concise README body and four approved images;
+  advance its heading and installed application metadata to 1.3.49.
+- See PyCForge-1.3.49-Verification.txt and
+  specifications/revision_performance_1_3_49.md for evidence and remaining scope.
+
+# PyCForge 1.3.48 — Bounded Python checks and responsive shutdown
+
+- Admit Python Check through the shared background-work budget, after explicit
+  editor/conversion requests and before passive observers. Show queue time
+  separately; the 60-second execution limit starts only after admission.
+- Wake queued scans on budget changes instead of repeating admission checks.
+  Canceling a queued request removes it without starting a worker.
+- Retire checker processes asynchronously and retain their capacity until exit.
+  Keep normal Qt shutdown alive through cleanup; remove the outline GUI wait.
+- Bound cumulative checker output and preserve current-source result checks.
+- Organize 30 searchable HTML Help pages, with a dedicated Python Check guide
+  and Previous/Next navigation matching the complete catalog. Correct the
+  README's outdated record-binding restriction and retain all four image links.
+- Preserve conversion behavior, Python save integrity, and runtime dependencies.
+- See PyCForge-1.3.48-Verification.txt for validation and native acceptance scope.
+
+# PyCForge 1.3.47 — Python save integrity
+
+- Compare linked Python files with the exact disk version last opened or saved.
+  Conflicting saves preserve local text and offer a bounded comparison, Keep
+  Editing, Reload from Disk, Save As, or an explicitly reviewed overwrite.
+- Recheck the reviewed disk version before replacement. Save All and exit stop
+  when a conflict remains unresolved; newer edits during saves remain dirty.
+- Keep disk monitoring independent of source edits and revision readiness.
+  Show persistent tab conflict state and recover watches after file replacement.
+- Coalesce repeated file notifications and allow only one assessment per path
+  at a time, with a final follow-up when another change arrives during reading.
+- Retain filename-derived identities, custom aliases, project checkpoints,
+  guarded archive saves, and the complete existing conversion implementation.
+- Preserve the README body, four approved image URLs, and project guidelines;
+  update its top version heading and the installed application version.
+- Reconcile historical save-identity and inventory checks with current behavior.
+- See PyCForge-1.3.47-Verification.txt for validation and native acceptance scope.
+
+# PyCForge 1.3.46 — Typed records in branches and loops
+
+- Initialize immutable record locals in if/elif/else, for/while and loop-else
+  regions, with a value proved present on every continuing path before a read.
+- Replace locals and record parameters with values of the same exact class.
+  Preserve earlier aliases, constructor evaluation order and parallel swaps.
+- Replay record flow evidence against normalized source before lowering.
+  Preserve earlier explicit profiles and existing single-assignment C output.
+- Extend installed HTML Help with complete branch, loop and parameter examples.
+- Preserve the README body and its four image URLs; update only the top heading
+  to v1.3.46, following AGENTS.md and PyCForge-README-Guidelines.txt.
+- Retain the v1.3.45 module-save and project-restoration corrections. Runtime
+  conversion, workspace implementation and runtime dependencies are unchanged.
+- See PyCForge-1.3.46-Verification.txt and
+  specifications/record_control_flow_1_3_46.md for scope and verification.
+
+# PyCForge 1.3.42 — Structured immutable Typed records
+
+- Read fields directly from constructors, factory results, nested records and
+  constant-indexed record collection elements; preserve evaluation order.
+- Support exact nominal nested record fields with bounded acyclic inline
+  layouts, and fixed local homogeneous record lists/tuples with ordered loops.
+- Replay source/collection evidence before emission; validate nested C types,
+  dependency order and const propagation. Keep earlier explicit profiles.
+- Fix private-field name-mangling conversion and reject late imports used by
+  nested record annotations before they are bound in Python.
+- Add complete executable HTML examples and synchronize existing Help limits.
+  README.md remains byte-for-byte unchanged; no UI or Runtime behavior change.
+- See specifications/record_structures_1_3_42.md and
+  PyCForge-1.3.42-Verification.txt for scope, checks and remaining limits.
+
+# PyCForge 1.3.41 — Typed record constructor expressions
+
+- Support direct record construction in returns and positional function
+  arguments, including branches, nested calls and imported class aliases.
+- Preserve exact nominal types and scalar field layouts. Stage arguments once
+  from left to right and return automatic struct values without heap storage.
+- Authenticate constructor expression evidence against the source and retain
+  explicit historical profiles with their previous constructor limits.
+- Add a complete reflection-and-distance example to HTML Help and update the
+  multi-module and separate C caller examples. Describe supported usage and
+  practical limits without development-cycle commentary.
+- Leave README.md byte-for-byte unchanged, including its version heading and
+  three approved image URLs, while conversion upgrades continue.
+- See specifications/record_expressions_1_3_41.md and
+  PyCForge-1.3.41-Verification.txt for technical scope and verification.
+
+# PyCForge 1.3.40 — Typed records across supplied modules
+
+- Import immutable record classes directly from their defining supplied module,
+  with optional aliases. Pass and return exact record types through imported
+  functions; allow record-only companion modules.
+- Preserve nominal class identity, scalar field layouts, value-copy C structs
+  and separate module exports. Authenticate imported aliases against retained
+  source and validate cross-module C types through declared dependencies.
+- Promote typed-record-modules-v1.3 / c-renderer-v1.3. Explicit historical
+  profiles retain their previous limits; Runtime conversion is unchanged.
+- Add an executable three-module geometry example to HTML Help, including
+  import rules, factory results, nominal typing and remaining call limits.
+  Restore the current-version footer on five existing Runtime Help pages.
+- Update only the README version and affected conversion coverage. Retain its
+  established prose, code examples, contact, bug tracker and exact three approved
+  image URLs. The existing screenshots remain accurately labeled 1.3.39.
+- Package no screenshots or design images; preserve the required app icons.
+- See specifications/record_modules_1_3_40.md and
+  PyCForge-1.3.40-Verification.txt for scope and verification.
+
+# PyCForge 1.3.39 — Typed record parameters and returns
+
+- Add nominal immutable record parameters, factory results, forwarding and
+  returns in Typed mode. Preserve exact field types and positional evaluation
+  order; reject mutation, mismatched classes and unsafe value uses.
+- Generate C structs passed and returned by value without heap allocation.
+  Include exact generated type names and record layouts in module export metadata.
+- Promote typed-record-values-v1.2 / c-renderer-v1.2 while preserving explicit
+  historical profiles. Runtime keeps its 1.3.38 conversion contract.
+- Expand executable HTML Help with complete Python and separate C caller
+  examples, copy semantics and clear module/call limits. Repair the Help catalog's
+  Runtime strings keyword count so all documentation pages can load.
+- Refresh the established README for 1.3.39 with the approved banner and two
+  exact Cloudinary screenshot URLs, current conversion coverage, and the five
+  confirmed 1.3.32 audit fixes above the retained contact details. Keep code
+  examples and application icon files unchanged; add no other README links.
+- Exclude screenshots and design images from release archives; retain only
+  required application icons and enforce this in distribution verification.
+- See specifications/typed_record_boundaries_1_3_39.md and
+  PyCForge-1.3.39-Verification.txt for scope and verification.
+
+# PyCForge 1.3.38 — Runtime text layout and normal editor scrollbars
+
+- Add Runtime center, ljust, rjust, zfill and expandtabs with Unicode character
+  widths, bound/expanded calls, argument validation, and bounded output work.
+- Default both Python panes to ordinary vertical/horizontal scrollbars. Retain
+  diagnostic, Find and ForgeLens navigation without the overlapping marker rail.
+- Fit gutters to the text viewport; correct orientation-specific handle sizing,
+  scroll-area corner painting and editor edge clipping in Python and Generated C.
+- Extend executable HTML Help; preserve README, dependencies and theme artwork.
+- See PyCForge-1.3.38-Verification.txt and specifications/text_layout_scrollbars_1_3_38.md.
+
+# PyCForge 1.3.37 — Editor feedback and Save As corrections
+
+- Show the saved filename in tabs, Source Bundle rows, source headers and window titles.
+  Preserve explicit module/logical identities and imports. Complete the visible save
+  projection before reporting success, including when snapshot delivery is delayed.
+- Put call signatures in the existing status strip; retain clickable completion lists.
+  Retire hints when their editor context changes without replacing newer status feedback.
+- Highlight function/class names without repainting def/class. Respect lexical string
+  and comment boundaries, multiline state resets and UTF-16 positions.
+- Distinguish source edits from syntax-format refreshes. Preserve authenticated fold
+  arrows, collapsed functions and source markers across format-only updates.
+- Update HTML workspace Help. Keep README, converter engines, matte theme and icons.
+- See PyCForge-1.3.37-Verification.txt and specifications/editor_feedback_1_3_37.md.
+
+# PyCForge 1.3.36 — Separate Typed C module exports
+
+- Export a fresh Typed conversion as one C source/header pair per module,
+  shared type declarations, and a machine-readable C ABI manifest in a ZIP.
+- Preserve validated function bodies and existing generated symbols. Resolve
+  helper dependencies per translation unit; keep support helpers internal.
+  Check portable filenames, C11 significant symbol prefixes and complete emission ranges.
+- Add File → Export C Modules in the existing matte custom chooser. Build archives
+  off the UI thread and atomically publish only while the exact Typed result is fresh.
+  Pending text/identity edits immediately retire export authority. Existing Save C,
+  ForgeLens and Compile continue to use the unchanged single-file result.
+- Document C parameter declarations, file status arguments and ownership.
+  HTML Help includes an executable API export and separate C caller; README unchanged.
+- Runtime exports still require a shared-context ABI design. No new Python syntax,
+  dependencies, stable cross-release binary ABI, or automatic record boundaries are claimed.
+- See PyCForge-1.3.36-Verification.txt and specifications/module_exports_1_3_36.md.
+
+# PyCForge 1.3.35 — Runtime text parsing coverage
+
+- Add rsplit, splitlines, partition/rpartition, and exact prefix/suffix removal.
+  Support Unicode whitespace/line boundaries, embedded NUL, bound methods,
+  keyword forms where Python permits them, and supplied-module parser helpers.
+- Charge text scanning/comparison work to the existing execution budget;
+  preserve terminal allocation/work failure semantics and arena ownership.
+- Extend HTML Help with executable configuration and filename parsing examples.
+  Keep the matte UI, README, dependency list and Typed contracts unchanged.
+- Verification details and platform limits: PyCForge-1.3.35-Verification.txt.
+
+# PyCForge 1.3.34 — Runtime text update modes
+
+- Add r+, w+, a+, and x+ UTF-8 file workflows in Runtime conversion.
+  Require successful seek between reads and writes. Append-update begins at
+  EOF and preserves append semantics; exclusive-update preserves existing files.
+- Reject nonzero read-derived bookmark writes before changing data.
+  Such bookmarks still replay reads. Tell/flush cannot bypass direction checks.
+- Keep budgets cumulative, avoid input-stream fflush, and close streams on
+  positioning failures. Internal file layout changed: regenerate C/rebuild callers.
+- Add HTML Help with three runnable examples, mode comparison and precise limits.
+  README, matte UI, dependencies and Typed conversion contracts stay unchanged.
+- Verification details and platform limits: PyCForge-1.3.34-Verification.txt.
+
+# PyCForge 1.3.33 — Universal matte interface and harpy eagle branding
+
+- Apply brighter graphite surfaces and solid matte buttons across the workspace,
+  menus, dialogs, reports, scan panels, Help, and Ting viewers. Hover, focus,
+  pressed, checked, disabled, and semantic feedback remain distinct.
+- Introduce the gray harpy eagle and steel-blue C lettering. Rebuild the 56-icon
+  PNG catalogue at nine sizes, including simplified eagle artwork for small UI
+  placements. No SVG assets are shipped.
+- Separate dialog resizing from maximizing. Compact prompts/settings remain fixed;
+  command and list dialogs resize where useful; large viewers explicitly offer
+  maximize/restore beside Close on the right. Move the Classes & Functions Copy
+  action into the right title-bar toolbar.
+- Keep About's system information inside compact displays and make the exact
+  registry fingerprint selectable in a read-only field. Own deferred dialog-focus
+  restoration with a timer that ends with the dialog. Fixed startup progress
+  still refits longer stage/failure messages, including larger UI fonts.
+- Update HTML Help with appearance and dialog-control guidance. README.md and
+  conversion/scan engines remain byte-for-byte unchanged from 1.3.32.
+- Verification details and platform limits: PyCForge-1.3.33-Verification.txt.
+
+# PyCForge 1.3.32 — Deep conversion audit corrections
+
+- Correct Runtime iterator retry and exhaustion state, including strict and
+  non-strict zip, recovered mapping mutation errors, and files rewound after EOF.
+- Consume complete dictionary input pairs before checking their arity, preserving
+  prior updates and fixed-target assignment's separate consumption rule.
+- Add native/Python interaction witnesses and audit the complete test inventory.
+- Release pending Tools and quick-view callbacks when their window is destroyed;
+  keep standard window controls inside the menu bar at narrow widths.
+- Refresh active release assertions without changing sealed conversion contracts.
+- Update HTML Help examples and retain README.md byte-for-byte.
+- Verification details and platform limits: PyCForge-1.3.32-Verification.txt.
+
+# PyCForge 1.3.31 — Runtime text bookmarks and exclusive creation
+
+Runtime UTF-8 file workflows now support tell and bounded seek: restore a
+bookmark on the same open handle, rewind, retain the current position, or
+move to EOF. Unicode/newline lookahead is preserved; file iteration's telling
+restriction is observed. Bookmarks are opaque, handle-local values, not
+character indexes or portable offsets. Host C long limits still apply.
+
+Mode x creates a new file without overwriting an existing destination.
+FileExistsError is admitted as a recoverable builtin exception, with OSError
+and Exception parent matching. Writes after creation can still leave partial
+files on failure. Conversion itself performs no source-program file I/O.
+
+Seeking never resets resource counters. Bookmark storage is released on all
+close paths; live-file collection refusal and closed-handle collection remain
+intact. Internal PFile layout changed: regenerate C and rebuild callers.
+No dependency, UI control, save workflow, or README changes.
+
+HTML Help adds File bookmarks and exclusive creation, with runnable examples,
+search entries, precise limits, and updated file/exception references. See
+specifications/runtime_file_positions_1_3_31.md and the release verification
+report. Native Windows acceptance remains outstanding.
+
+Queued work includes separate C-module exports, binary/update file profiles,
+Typed record boundaries, and automatic collection with live temporary roots.
+
+---
+
+# PyCForge 1.3.30 — Explicit Runtime memory reclamation
+
+C callers can now use pv_collect between completed Runtime calls to reclaim
+unreachable values and cycles while retaining supplied PV roots and context
+state. Precise, non-moving tracing covers closures/defaults, shared containers,
+objects/methods, iterators/views, module bindings, and closed file handles.
+Released file-read buffers also return retained-file capacity.
+
+Collection is opt-in at idle C-call boundaries. It does not run inside Python
+loops or automatically at allocation failure, and it does not reset work/file
+budgets. Active calls/files, errors, invalid root metadata, and collector
+scratch allocation failure refuse collection before any sweep. Retained PVs
+must be supplied on each call; raw pointers alone are not roots.
+
+Internal allocation/closure layouts changed: regenerate C and rebuild callers
+together. Existing no-collection callers keep their original arena lifetime.
+No dependency, UI component, save workflow, or README changes.
+
+HTML Help adds Runtime memory and collection with a verified C caller and
+updates lifetime/file-budget guidance. See specifications/runtime_collection_1_3_30.md.
+Automatic collection within executing functions remains separate work requiring
+live temporary roots. Other queued upgrades include module .h/.c exports,
+expanded file profiles, and Typed record boundaries.
+
+---
+
+# PyCForge 1.3.29 — Runtime validation and ForgeLens
+
+Runtime conversion now records exact source-to-C emission ranges and checks
+final output through a separate validator before publication. Checks cover
+source identities and AST ranges, complete output byte coverage, Unicode
+coordinates, C lexical balance, callable declarations/definitions, and local
+jump destinations. ForgeLens uses the established authenticated workspace
+integration. Shared Runtime support remains C-only.
+
+PYC4698 reports internal validation failures without publishing new C. PYC4699
+continues to explain Runtime's contract: structural/provenance checks do not
+prove semantic equivalence or replace external compilation and testing. The
+Typed C-IR proof pipeline and Runtime arena lifetime remain unchanged.
+
+The requested scan/diagnostics audit found and fixed quick diagnostic navigation
+for untouched CRLF/CR files. Real edits, including edit followed by undo, still
+retire old diagnostic and scan locations. No replacement controls or new
+save workflow; the existing theme and components are retained.
+
+HTML Help adds Runtime validation and ForgeLens, with a verified example and
+updated contract/inspection guidance. README remains byte-for-byte unchanged.
+
+Next conversion work: value reclamation for long-running contexts, separate
+C-module exports, expanded file profiles, and Typed record boundaries.
+See specifications/runtime_validation_1_3_29.md and the verification report.
+
+---
+
+# PyCForge 1.3.28 — Runtime exception recovery
+
+Runtime conversion now supports selected `try`/`except`/`else`/`finally`
+control flow and builtin raises with optional literal messages. Matching
+handlers recover from ordinary runtime errors across calls and supplied
+modules. Cleanup preserves nested return, break, continue, and error order;
+file contexts close before control reaches an enclosing handler.
+
+Exception names are a closed documented set. Exception objects, `as` bindings,
+bare re-raise, chaining, exception groups, and custom exception classes remain
+unsupported with PYC4630 diagnostics. Allocation and execution-resource
+failures stay terminal: Python cleanup bodies are skipped after exhaustion,
+while automatic file cleanup still runs. Runtime context lifetime and the
+remaining ForgeLens/C-IR limitations are unchanged.
+
+HTML Help adds Exceptions and cleanup with executable examples, searchable
+reference entries, supported boundaries, and file/error guidance. README is
+byte-for-byte unchanged from 1.3.27. No dependency or save-control changes.
+
+This is the first stage of the accepted conversion upgrade program. Runtime
+validation/mappings, value reclamation, separate C-module exports, expanded
+file profiles, and Typed record boundaries remain subsequent work.
+See specifications/runtime_exceptions_1_3_28.md and the release verification
+report for scope and measured evidence.
+
+---
+
+# PyCForge 1.3.27 — Immediate stale Python scan results
+
+- Scanned-source edits immediately disable retained findings in both the full Python check dialog and recent-scan dropdown.
+- Stale panels are visibly muted and label their locations as scanned lines. Clean results also stop presenting themselves as current after an edit.
+- Invalidation persists through undo, hidden dialogs, renames and closed tabs until a new scan completes for unchanged source.
+- Changes to included companion modules invalidate the same scan; unscanned modules and tab switching alone do not.
+- Scan results completed after an intervening edit remain stale.
+- Navigation rejects old finding objects and queued callbacks from earlier scans, with a final freshness check before highlighting.
+- Preserves Windows newline normalization, existing scan analysis and conversion diagnostics behavior.
+
+# PyCForge 1.3.26 — Conversion diagnostics quick view
+
+- Added a separate amber warning-triangle button beside Tools.
+- Enabled only for current rejected/failed conversions that have Diagnostics records.
+- Opens a compact native dropdown with the same severity, code, module/line and message as the Diagnostics tab.
+- Clicking a located item selects its source module and highlights the reported range.
+- Source edits immediately close the list and disable access, including edits before delayed synchronization and edits in the split view.
+- Undo does not revive an invalidated result. Convert again to obtain fresh diagnostics.
+- Renaming/closing source, changing the source bundle, or starting another conversion disables old navigation.
+- Tab changes alone preserve valid results. Diagnostics without source locations remain readable but cannot navigate.
+- Long rows are elided with full tooltips; long lists scroll within the screen.
+- The Diagnostics tab, Python scan and conversion engine behavior are unchanged.
+
+# PyCForge 1.3.25 — Split Tools control and recent scan results
+
+- The wrench opens the regular Tools menu; the adjacent arrow opens recent Python scan results.
+- The divider has a clear gap before the two-part button.
+- The compact, scrollable dropdown reuses the scan dialog's findings, source navigation and dismissal state.
+- Distinct feedback covers no scan, an active scan, no errors/issues, removed findings and stale source.
+- Open full scan returns to the existing dialog; opening the dropdown never starts a scan.
+- Popup closure resets pressed and hover styling, including repeated menu action use.
+- Retains the v1.3.24 removal of the expandable scan scope row.
+
+# PyCForge 1.3.24 — Python check dialog cleanup
+
+- Removed the expandable Scan scope and limits row and its module/function count.
+- The results panels now have more vertical room.
+- Analysis notes remain available in the existing scan-status tooltip.
+- Scan logic and clickable issue-panel behavior are unchanged.
+
+# PyCForge 1.3.23 — Deeper Python code checks
+
+Check Python Code now follows supported top-level statements as well as functions.
+Explicit return, raise, break and continue paths survive loop and finally analysis.
+The checker models try/except/else/finally and conservative context-manager
+suppression, and tracks exception-target deletion. Findings explain the relevant
+assignment path or helper location.
+
+Bounded argument-sensitive helper analysis follows arguments, aliases, defaults and
+return values. Optional “Use open modules to trace imports” supplies unsaved companion
+source without importing or executing it. Findings remain on the selected tab;
+edits, renames or closure of any supplied tab make the retained scan stale.
+The scope/limits text is expandable so longer explanations do not crowd the panels.
+
+The four existing compiled Ting decision packs remain unchanged; the upgrade improves
+the evidence and paths they evaluate. Rule tests are retained, with new paired bug/clean
+regressions and authored runtime witnesses. Dynamic/unsupported analysis is explained.
+This checker addresses Python correctness only and adds no conversion-compatibility
+checks. Conversion support remains documented in the existing HTML reference.
+
+Limits: 16 modules, 1 MiB per module / 2 MiB total, 50,000 AST nodes per module,
+256 functions, 512 call contexts, 10 call levels, 100,000 flow operations,
+2,000 candidate facts, 200 displayed findings and 60 seconds.
+No dependencies are added; packaging remains one wheel. Native Windows interaction
+is to be verified with the supplied checklist.
+
+---
+
+# PyCForge 1.3.22 — Python code checker
+
+The Tools menu is now a wrench dropdown after the text menus and separator.
+Check Python Code appears above Run Python; F5 still opens Run Python.
+
+The modeless checker scans the selected tab’s current unsaved text in a cancellable
+worker. It combines Python syntax checks with four dedicated compiled Ting packs
+for assignment/reachability, supported None-value uses, local-call arguments and
+mutable defaults. Local function-return summaries support deeper findings without
+running or importing the program. Confirmed, conditional and review findings are
+kept distinct; unsupported analysis is reported in the dialog.
+
+A stage label, percentage bar and elapsed time accompany the scan. Results appear
+as stacked clickable cards: choosing one returns to the original tab and highlights
+its source. Cards and scroll position survive reopening. Right-click Remove dismisses
+a card; Re-scan replaces the results. Source changes mark retained results stale and
+block outdated navigation. Cancel or closing an active scan clears all panels and
+shows “Scan was halted.” There is no HTML export or automatic source editing.
+
+Limits: one tab, 1 MiB, 50,000 syntax nodes, 256 functions, 2,000 candidate facts,
+200 displayed findings and 60 seconds. Flow analysis covers supported function bodies;
+external imports, runtime-dependent behavior and complex control flow remain outside
+this first rule set. A clean scan is not a correctness guarantee.
+
+README and offline Help receive concise usage additions. Existing conversion behavior,
+the conversion bug tracker, dependency list and one-wheel packaging are retained.
+Native Windows/macOS interaction remains a separate platform verification step.
+
+---
+
+# PyCForge 1.3.21 — Internal audit corrections
+
+- F01: Track every active container during Runtime representation; preserve tuples inside sets/frozen sets and real list/dictionary cycles.
+- F02: Preserve negative zero when compensated summation has a zero correction, including the fallback materialization path.
+- F03: Reject Windows COM/LPT superscript-digit device aliases in every project path component.
+- F04: Permit project-checkpoint wording while retaining checks for obsolete converter-status labels.
+- F05: Maintain the current multiple-inheritance corpus expectation across release increments; keep historical overrides.
+- F06: Remove unread Typed locals only when all assignments are side-effect-free string literals and annotations agree; retain calls and potentially failing expressions.
+- F07: Use the current module-identity widget's public text API in the retained acceptance test.
+- R01: Project the latest snapshot before Python-open completion callbacks; wait for projected UI readiness in the split-view lifecycle regression.
+
+The README adds a dedicated conversion bug tracker immediately before contact information. HTML Help content and installation dependencies are unchanged. Native Windows and macOS verification remains a separate platform check.
+
+---
+
+# PyCForge 1.3.19 — Project bundles and filesystem reliability
+
+File → Project saves and opens portable .pcfproj bundles with a module preview,
+loading cover, named checkpoints, comparisons, and guarded restoration. Project
+saves preserve editor text independently of the linked Python files. Opening a
+bundle uses a new working folder; startup reconnects history without extracting
+older source over disk files.
+
+The filesystem audit adds protection against Save As aliases of another open
+module, clears old failed session paths after explicit project replacement,
+preserves existing bundle permission modes, and bounds startup history reads.
+Missing, damaged, slow, or invalid history locations appear in the Startup report
+without preventing use of the workspace. Save and restore failure paths retain
+the previous bundle and unsaved editor state.
+
+The searchable HTML Help includes a dedicated Projects and checkpoints page.
+The README retains its existing structure with a concise project-bundle section.
+The package version is 1.3.19. Existing historical files remain in the source
+archive; no conversion dependency or conversion behavior is changed.
+
+---
+
+# PyCForge 1.3.14 — Save All Python and shutdown verification
+
+File → Save All Python saves new and modified modules in order, asks for
+locations only when needed, and keeps the selected tab unchanged. The command
+is also available in the command palette. Save Python still applies to the
+selected tab; Save Python As remains available when no Python save is active.
+
+Save All and exit now share sequential asynchronous saves, avoiding overflow
+of the bounded file queue. Save commands cannot overlap. Cancellation and write
+failure release the busy state and leave unsaved modules open. Edits made while
+saving remain unsaved and prevent automatic closure. Exit also includes
+never-saved modules and waits for any individual save already in progress.
+
+Shutdown detaches both source views before their shared text buffers are
+released, preventing repaint against a deleted Qt document. Startup settings,
+conversion behavior, the external Python launcher, README, dependencies and
+version metadata are unchanged. Help explains saving and the distinction
+between the script console and the original Windows console.
+
+The final Linux/offscreen Qt suite passed 298 tests and 773 subtests, with no
+skips. Coverage includes 64-module saves and exit, immediate edits in both
+views, retries after failure/cancellation, repeated Save/Close, deferred buffer
+cleanup, fresh startup, session restoration and corrupt-settings recovery.
+Windows/macOS console construction is mocked; native desktop testing remains
+required. See PyCForge-1.3.14-Save-All.txt for installation and laptop checks.
+
+---
+
+# PyCForge 1.3.14 — Run Python and per-tab save state
+
+Tools → Run Python… (F5) opens a modeless, themed command dialog for the
+selected Python tab. Saved modules supply their absolute path and working
+folder automatically. Unsaved or modified modules show “Run Python — Module
+not saved” in the custom titlebar and disable the command box and Run button.
+The dialog follows saves and tab switches; it never saves or executes source
+merely because it was opened.
+
+The editable default uses the Python environment running PyCForge. Windows
+opens cmd.exe /k with console Python; Linux uses an installed terminal and
+retains the exit status/output; macOS opens Terminal. Run Python is separate
+from conversion and C compilation. Save Python now reflects the active tab's
+unsaved state in both the toolbar and File menu. Save Python As stays available.
+
+The application and distribution retain version 1.3.14. The converter, C build
+service, Ting runtime, README and Python dependencies are unchanged. Offline
+Help documents the commands. The focused/adjacent suite passed 226 tests and
+769 subtests on Linux with offscreen Qt. Real POSIX execution checks include
+relative file access, sibling imports, interactive input, arguments, unusual
+path characters and Python errors. Windows/macOS launch construction is
+covered through mocks; native desktop terminal checks remain for those hosts.
+See PyCForge-1.3.14-Run-Python.txt for installation and laptop checks.
+
+---
+
+# PyCForge 1.3.14 — UI review follow-up
+
+Keep the application and distribution version at 1.3.14 as requested.
+Completion suggestions now reject native window activation during mouse clicks,
+so scrollbar interaction retains editor focus. PgUp and PgDn navigate suggestions
+without moving the source caret. The compiler dialog uses an inset dropdown
+button and the existing down-chevron asset to preserve each field's outline.
+
+All 118 focused and adjacent regression tests and 652 subtests pass. The 24 UI
+cases also pass at 125% and 150% display scaling. A GCC build through the dialog
+succeeds and the executable returns the expected result. Validation uses Linux
+with Qt's offscreen backend; the Windows laptop interaction needs confirmation.
+
+Only two application source files change. README, screenshots, contact details,
+Help, conversion/build services, dependencies, and version metadata are retained.
+See PyCForge-1.3.14-UI-Review.txt for evidence and laptop checks. To replace an
+already-installed 1.3.14 from the updated local wheel, use --force-reinstall.
+
+---
+
+# PyCForge 1.3.14 — Help and README refresh
+
+Review and refine all 21 offline Help pages without changing conversion behavior.
+Seven restrained PyCForge caveats boxes explain integer bounds, context ownership,
+string construction, set ordering, annotation checks, cooperative inheritance,
+and file-write cleanup beside the relevant examples. A complete cooperative
+constructor diamond adds one runnable example; the existing examples are retained.
+
+Correct stale class limits, mode-specific module guidance, dependency wording,
+page links, and API-page navigation. Refresh the README's conversion and compiler
+coverage while retaining its introductory organization, starter examples, and
+exactly its two original screenshot links and image assets.
+
+The application version is 1.3.14. Converter contracts remain at their existing
+versions, including Runtime 1.3.13; converter/build sources and dependencies are
+unchanged. See PyCForge-1.3.14-Documentation-Review.txt for the page-by-page review
+and the executed documentation checks.
+
+---
+
+# PyCForge 1.3.13 — multiple inheritance conversion
+
+Runtime mode now converts multiple inheritance between declared classes with
+Python C3 method ordering, cooperative super calls, shared diamond fields,
+constructor selection, and subtype recognition through every base. Imported
+and re-exported bases retain their identity. Duplicate bases, inconsistent
+orders and field/method collisions reject conversion with source diagnostics.
+The complete ancestor closure remains bounded to 64 user classes plus object.
+
+Existing single inheritance and flat ordinary method dispatch are retained.
+No package dependency was added. Properties, static/class methods, dynamic
+bases and custom descriptors remain outside the documented class profile.
+See specifications/multiple_inheritance_1_3_13.md and the release verification
+report for the contract and measured checks.
+
+---
+
+# PyCForge 1.3.4 — Classes & Functions loading panel
+
+- Cover the complete tree area, including its header, with a themed panel while definitions are parsed and tree rows are populated.
+- Center a short 88 × 8 progress bar on the panel, with no visible loading text.
+- Reveal the tree and restore keyboard focus when loading finishes; stop the indicator on errors, source changes, or dismissal.
+- Preserve double-click and Enter navigation and the title-bar Copy action.
+- No new application dependencies or conversion changes.
+
+Validation: 37 focused tests and 50 subtests passed on Linux with offscreen Qt. Themed loading and loaded states were visually checked. Native Windows verification and a full-suite rerun were not performed for this patch.
+
+See PyCForge-1.3.4-Loading-Panel.txt for the exact scope and evidence.
+
+# PyCForge 1.3.3 — editor integration corrections
+
+- Completion preserves selected prefixes and rejects results after Escape, selection changes, or leaving the editor.
+- Delayed Go to Definition results retire when the caret, focus, or user intent changes.
+- Lambda parameter rename retains unrelated bindings and explicit keyword callers.
+- Document formatting accepts line movement around type-ignore directives while checking that each directive still covers the same statements.
+- Selection formatting handles repetitive source without false boundary errors and preserves unselected text.
+- Includes the split-view close, Find toggle, window-control hover, Generated C hover, and steady fold-arrow corrections.
+- Keeps all existing conversion coverage and unpinned application dependencies.
+
+# PyCForge 1.3.1 — reliability update
+
+This is one cumulative update to the complete PyCForge application.
+
+Installation/splash correction, keeping version 1.3.1:
+- Declare PySide6, NumPy, Numba, Jedi and autopep8 by name without dependency version pins.
+- Check numeric dependency presence without comparing version numbers; retain real import/kernel readiness checks.
+- Fit the complete splash icon, subtitle descenders and wrapped failure details using layout size hints.
+- Give Cancel/Close initial keyboard focus so the title-bar X does not appear stuck highlighted.
+- Resolve parameter rename references safely with both tested Jedi generations, preserving unrelated same-named globals.
+
+- Bind deferred Qt callbacks to their owner and release pending generated-C projection on shutdown.
+- Reject non-regular preview inputs without blocking on POSIX named pipes; retain UTF-8 and size checks.
+- Reap an outline child and close its handles if process startup raises after creating it.
+- Publish immutable source-token records incrementally to avoid holding two complete dictionary trees.
+- Enforce Typed token budgets during tokenization, preserving supported conversion output and diagnostic codes.
+- Preserve all Typed/Runtime, module/file, editor, Jedi/autopep8, tooltip, gutter and PCFC11 features.
+
+See PyCForge-1.3.1-Reliability-Audit.txt for exact findings, measurements, validation and remaining native-platform checks.
+
+# PyCForge 1.3.0 — complete consolidated release
+
+One installation now contains the complete 1.1.12 advanced conversion/editor
+line plus the 1.2.2 PCFC11 integration and additional resource-lifecycle fixes.
+There is no choice between conversion coverage and compilation support.
+
+- Both Typed and Runtime modes; runtime strings, lists, dictionaries, classes,
+  closures, comprehensions, everyday builtins/formatting, supplied modules and
+  connected UTF-8 file workflows are retained.
+- Current editor tools, shared work admission, bounded caches, Open/New Module
+  recovery and fold-marker fixes are retained.
+- PCFC11 dialog focus and custom compiler/output chooser fixes are included.
+  Object and executable builds accept both conversion ABIs. Runtime executable
+  adapters handle errors and destroy their value context before returning.
+  Windows UCRT compatibility headers supply runtime declarations missing
+  from PCFC11 0.1.1; Windows assembly generation is checked at O0 and O1.
+- Cancelled application startup now finishes and releases its modal dialog,
+  preventing it from blocking subsequent windows and keyboard shortcuts.
+- Conversion cancellation is retained throughout request encoding/spawning; idle
+  service frames release payloads. Modal children are destroyed; hidden timers
+  stop. Slow file previews cannot keep the interpreter alive through Qt's pool.
+  Regular workspace file reads are bounded to 16 MiB and reject special files.
+- The README and 21 offline Help pages describe the combined application.
+  Existing screenshot links and advanced runtime implementation are preserved.
+
+PCFC11 remains a separately installed compiler with a system assembler/linker.
+The package adds no dependency beyond those already required by 1.1.12.
+Native Linux validation is recorded in evidence/consolidation. Native Windows
+acceptance and actual laptop energy measurements remain outstanding. Runtime
+values retain their documented arena lifetime; whole-process memory is not
+bounded by the arena budget. No PyPI publication was performed.
+
+The evidence/consolidation directory records this release's checks. Historical
+release notes and evidence below describe their original versions only.
+
+---
+
+# PyCForge 1.1.12 — resource ownership and process reliability
+
+This patch updates 1.1.11. Closed temporary dialogs and their filesystem models
+are destroyed after use; About clocks run only while visible. Idle conversion
+supervisors wait for work, and idle service threads release completed payloads.
+Conversion pipe transfers cannot block cancellation or shutdown. Malformed
+worker envelopes trigger process reclamation, and reaped process handles close.
+
+The app, package metadata, About, startup, Help and reports use the same product
+version. Converter source, semantic contracts, dependencies, and HTML Help
+content are unchanged. Earlier editor lifecycle and About improvements remain.
+
+Measured evidence, reproduced baseline failures, scope and native Windows
+acceptance steps are in evidence/resource_audit. These checks do not certify
+battery life or the absence of every possible resource leak.
+
+# PyCForge 1.1.11
+
+The About dialog omits the Ting Shadow / Advisory badge. Application version
+metadata, window titles, startup, About, Help and package metadata use 1.1.11.
+
+- Fix the empty-workspace marker refresh after closing the last Python tab with generated C visible.
+- Recover stale Source Bundle selections so Open Python and New Module remain usable.
+- Restore fold markers on module changes and syntax highlighting without parsing large source on the GUI thread.
+- Cover rejected transpilation, late callbacks, pending edits, shared gutters, and repeated close/reopen cycles.
+
+# PyCForge 1.1.10 — connected UTF-8 file workflows
+
+Runtime functions can now read text, process it through local or imported
+helpers, and write or append results. Scoped open calls support character-sized
+reads, line iteration/readlines, write/writelines, flush, and early close.
+UTF-8 contents support embedded NUL; paths support Unicode and reject NUL.
+Newline=None and newline="" have distinct documented translation behavior.
+
+Cleanup covers normal exits, return, break, continue, failed later opens, and
+runtime errors. Handles passed to helpers share their cursor; returned text
+outlives its handle. Per-context limits bound open handles, operations, retained
+read buffers, and per-handle input consumption. Obsolete transient read buffers
+are reclaimed while public values retain the established arena lifetime.
+
+The 21-page HTML Help is a user manual with no development-cycle status. It
+adds complete read/process/write examples, a three-module report, input and
+expected output files, operation tables, newline rules, and error guidance.
+Stale module-limit and install examples were corrected. README retains its two
+original screenshot links and 200-line limit. Dependencies are unchanged.
+
+Typed file functions retain their external status-pointer ABI; connected file
+calls use Runtime mode. Exception recovery, independent runtime C-IR validation,
+and exact runtime ForgeLens mappings remain outside this delivery. PYC4699 is
+retained. Native Windows acceptance is pending; no PyPI publication occurred.
+See specifications/runtime_files_1_1_10.md, fixtures/runtime_files_1_1_10, and
+evidence/files_1_1_10 for the contract, runnable report, and validation evidence.
+
+---
+
+# PyCForge 1.1.9 — runtime programs across supplied files
+
+Runtime conversion now accepts explicit source bundles. Named imports, module
+aliases, re-exports, imported classes/functions/constants, and immutable
+scalar/tuple module constants work with the existing runtime operations.
+Namespaces remain separate. Imports and defaults initialize in source order,
+once per C context; remaining supplied files initialize as explicit roots.
+
+The workspace converts all open documents. CLI conversion/validation accepts
+repeated `--module ID=PATH` and `--module-id ID`. C runtime failures now preserve
+the logical source file and line. Runtime artifacts can be inspected with the
+CLI. No installation dependency changed.
+
+Relative/star/local/conditional/cyclic imports, implicit packages, file discovery,
+writable globals, and general module execution remain excluded. Runtime file
+I/O and exception recovery remain the next coverage work. Runtime C-IR proof
+validation, exact ForgeLens mappings, and reclamation during a context lifetime
+remain unfinished. The development warning is retained. Windows acceptance is
+pending; no PyPI publication is part of this release.
+
+See `specifications/runtime_modules_1_1_9.md`, the four-file invoice fixture,
+and `evidence/modules_1_1_9/` for contracts, examples, and recorded verification.
+
+---
+
+# PyCForge 1.1.8 — everyday runtime conversions
+
+Runtime conversion now implements sum, min/max (key/default), abs, round,
+any/all, stable sorted and list.sort (key/reverse), lazy enumerate and zip
+(including strict), iter/next, and builtin function values such as key=abs.
+Lists add extend, pop, insert, remove, reverse, clear, copy, and index; tuples
+also add index. Shared list identity is preserved through mutations.
+
+F-strings, format(), and str.format() share bounded precision, width,
+alignment, sign, grouping, decimal/base and floating presentation. !s/!r/!a,
+named/numbered fields, field access, and nested width/precision are supported.
+Print/str/repr/ascii now render nested lists, tuples, dictionaries and views,
+including cycle markers. Numeric rounding uses exact binary64 decimal digits.
+
+Select Transpile → Runtime; the CLI uses --runtime-values. No installation
+dependencies changed. The README retains exactly its two screenshot links.
+The existing 20-page HTML Help now documents these operations and examples.
+
+Runtime remains a bounded development backend: one source document, no imports,
+module assignments, file I/O, exception recovery, generators or runtime sets.
+Integers are checked int64; floating sums follow Python 3.12 compensated summation.
+Formatting excludes locale-sensitive n, character c, z and custom protocols;
+width is at most 1,000,000 and precision at most 1,000. Numeric formatting needs
+C numeric locale and round-to-nearest. Values remain owned until pv_destroy().
+Exact ForgeLens mappings and the typed C-IR validation path are still absent.
+Native Windows acceptance and PyPI publication have not been performed.
+
+See specifications/runtime_values_1_1_8.md for the conversion contract and
+tests/test_everyday_runtime_1_1_8.py for native comparisons against Python.
+
+---
+
+# PyCForge 1.1.7 — editor responsiveness and correctness
+
+This release batches occurrence selection and caret merging, removes fold parsing
+from gutter painting, and fixes the large-document replacement transition.
+Unchanged documents reuse byte-bounded position and outline caches. Outline
+parsing runs in a persistent, cancellable process and extracts symbols without
+building conversion IR. A shared work budget prioritizes explicit operations,
+limits admitted CPU work to one or two jobs, and defers passive observers while
+typing. Current immutable source snapshots are shared between editor consumers.
+
+Editor workers retain bounded exact-request replies; formatting diffs are built
+in the worker. New edits still invalidate publication and preview authority.
+Cancellation stops active outline parsing, and obsolete revision indexes check
+for cancellation during scanning. Closed documents leave the document caches.
+
+Correctness fixes preserve multiple carets across physical modifier presses,
+prevent extra quote insertion inside comments/strings, replace the existing
+identifier tail when accepting completion, keep selection formatting inside its
+original lines, and correct form-feed navigation offsets. Unsafe inheritance,
+class-private, Unicode-alias, and decorated-parameter renames are refused with an
+explanation. Atomic saves retain existing permission modes and follow symlink
+targets rather than replacing the link.
+
+The typed/runtime converter implementations and dependency requirements are
+unchanged. Both README screenshot URLs are preserved. Local Qt measurements,
+regression results, and a focused Windows acceptance checklist accompany this
+candidate. Native Windows acceptance is pending; local timings are not a
+cross-platform input-to-display guarantee. No PyPI publication was performed.
+
+---
+
+# PyCForge 1.1.6 — professional Python editing
+
+This release adds smart pairs and selection wrapping, up to 256 simultaneous
+cursors, regex and selection-scoped search, previewed replacement across open
+source documents, offline completion and parameter hints, definition navigation
+with return, current-document scope-aware rename with preview, and explicit
+undoable formatting of a document or selected lines.
+
+Edit now has compact Selection, Lines, Find and Replace, Code, and Folding
+Functions submenus. All native menu surfaces are bounded to the current monitor
+work area, using More Commands submenus for overflow. The existing toolbar is unchanged.
+
+Jedi 0.19.x and autopep8 2.3.x are new installation dependencies; parso and
+pycodestyle are installed with them. Editing runs offline. Source analysis and
+regex searches run in deadline-bound processes, use source as data, and reject
+stale results. No backups, autosave, recovery snapshots, or source execution were
+added. The Python-to-C converter implementations are unchanged from 1.1.5.
+
+Rename is limited to statically resolved references in the current document,
+refuses name collisions, and preserves imported exports with explicit aliases.
+Dynamic string lookups and references in other documents require manual review.
+Formatting checks syntax-tree equivalence before applying. Analysis accepts
+500,000 characters per document; search previews accept up to 64 open documents,
+4 million characters total, and 2,000 matches. Oversized results are not applied.
+
+Automated validation and native Windows acceptance status are recorded in the
+release evidence and Windows checklist included with the distribution bundle.
+
+# PyCForge 1.1.5 — conversion mode selection and C scrollbar
+
+The Transpile menu now contains exactly two mutually exclusive checked choices:
+Typed and Runtime. Choosing a mode does not convert. The existing Transpile
+button and Ctrl+Enter execute the selected mode; the choice is remembered
+between launches, initially defaulting to Typed. Mode changes retire the previous
+result so it cannot be saved as current until conversion succeeds again.
+
+Generated C now uses its normal scrollbar without the dense mapping overview
+strip. Search, mapping navigation, read-only output, and ForgeLens highlighting
+remain available. The hidden strip performs no marker overview projection.
+
+No backup, autosave, recovery, snapshot-history, compiler, or other suggested
+feature is added. The typed and runtime conversion capabilities are unchanged
+from 1.1.4. CLI and Python API mode selection are unchanged. Both README
+screenshot URLs are preserved. Native Windows acceptance remains pending.
+
+---
+
+# PyCForge 1.1.4 — ordered runtime dictionaries
+
+Runtime value conversion now handles ordered mutable dictionaries, dictionary
+comprehensions, dict[K, V] annotations, scalar/immutable-tuple keys, key deletion,
+and get/setdefault/update/copy/clear/pop/popitem. Live keys/values/items views
+support iteration, length, truth, membership, and list/tuple snapshots.
+
+Shared references, first-insertion order, equal numeric keys, definition-time
+defaults, and nested mutable values are preserved. A hash index supports ordinary
+lookup workloads. Memory, work, missing-key, key-type, and iterator mutation
+checks use the existing C context. Active dictionary iterators permit value
+replacement and reject structural key changes, including equal-size changes.
+
+The existing runtime action, CLI, and API expose these additions. Searchable
+HTML help, the supported-conversions table, README, and examples describe the
+implemented forms and boundaries. Both README screenshots retain their URLs.
+No new dependencies, source execution, embedded C compiler, or PyPI publication
+are introduced. See specifications/runtime_values_1_1_4.md and the new tests.
+
+This is a development candidate with a documented Python subset. Native
+Windows acceptance remains outstanding; performance needs workload benchmarks.
+
+---
+
+# 1.1.3 — 2026-10-12
+
+The runtime value converter now implements default arguments, named keyword
+calls, positional-only and keyword-only parameters for functions, methods,
+constructors, and lambdas. Defaults are evaluated at definition time and keep
+shared mutable values; lambda defaults can capture each comprehension value.
+
+Unicode lower/upper, strip/lstrip/rstrip, whitespace and explicit-separator split
+with maxsplit, numeric text parsing, optional integer bases, finite float
+formatting, simple f-strings, print sep/end, and empty scalar/container
+constructors are implemented. Unsupported calls on known receiver types have
+source diagnostics. Ryu supplies shortest binary64 decimal formatting under its
+Boost license; Unicode case data is pinned to Unicode 15.0.
+
+The README and installed HTML help describe these operations as supported
+features, include runnable examples, and retain the two screenshot-only README
+links. The existing typed converter, PySide6 workspace, Ting runtime, splash,
+and PlutoAI boundary remain in place. No PyPI publication is performed here.
+
+Validation is recorded in `evidence/coverage_1_1_3/validation_report.json`.
+The preceding 1.1.2 audit and its evidence are retained below as history.
+
+---
+
+# 1.1.2 — 2026-10-12
+
+Correctness audit fixes: integer true division now rounds the exact int64 ratio; bound methods compare by receiver identity and method; duplicate runtime parameters and writes to Python's read-only __debug__ binding reject; the default converter accepts the minimum signed 64-bit literal. Corrected Unicode diagnostic spans, syntax-error positions, and bare-CR source tokenization. Guarded breadcrumb updates when the workspace is empty or closing. Native regression tests cover both conversion paths. See docs/CONVERSION_AUDIT_1_1_2.txt and evidence/correctness_1_1_2/validation_report.json.
+
+Added an opt-in runtime-values Python-to-C preview based on 1.1.1; runtime strings, mutable class/list aliases, mixed tuples/lists, annotated unions and containers, comprehensions and captured lambdas. Updated embedded Ting execution to 0.10.0a21 with NumPy/Numba dependencies and background numeric warmup in the splash. No C-to-assembly integration; that work is in PlutoAI. See specifications/runtime_values_1_1_2.md for exact limits.
+
+# 1.1.1 — PyPI README correction
+
+- Remove badges and relative documentation links from the PyPI README.
+- Retain only the two unchanged Cloudinary screenshot URLs.
+- Remove the outdated PDF reference and direct users to installed Help.
+- Validate the rendered README against the exact screenshot-only link policy.
+- Conversion behavior remains unchanged from 1.1.0.
+
+# 1.1.0 — Scalar and string conversion expansion
+
+This release expands conversion, with the new default profile
+`scalar-strings-v1.1` paired with `c-renderer-v1.1`.
+
+- Checked int/float/bool/str locals, declarations without initializers, chained
+  scalar assignments, flat unpacking/swaps and scalar augmented assignment.
+- Static module declarations and assignments, constant expressions, aliases
+  and source-order updates, frozen before entry-function calls.
+- Runtime UTF-8 code-point length, content comparison, prefix/suffix checks,
+  search and membership; bounded compile-time construction and string methods.
+- Explicit source-span evidence, exact helper plans and independent serialized
+  validation. Existing definite-assignment and representation checks remain.
+- Six existing TING agents receive the new strategy identity. Their unchanged
+  artifacts reproduce byte-for-byte through the private compiler.
+
+Dynamic owned-string construction and mutable globals remain unsupported.
+External C callers must satisfy the documented borrowed UTF-8 ABI. Historical
+profiles are still selectable. Desktop appearance, screenshots and links are
+preserved. See `specifications/scalar_strings_1_1.md` for the complete contract.
+
+This is a locally tested release candidate; it has not been uploaded to PyPI.
+Validation details are in `evidence/scalar_1_1/validation_report.json`.
+
+# Changelog
+
+## 1.0.5 — Focused IDE refinement
+
+Reduced all non-editor UI text by one point while preserving the Python and
+generated-C editors at 14 pt and 12 pt. Added restrained glass depth to controls,
+wider squarer scrollbars, slim illuminated state lines for the generated-C and
+Details toolbar toggles, and a gradient-backed Help navigation rail.
+
+Removed the Python indentation-guide overlay and its setting. Function-fold
+layout now synchronizes each shared source view immediately, moves cursors out
+of newly hidden blocks, preserves access to the final function at the scroll
+boundary, and remains stable while Generated C is repeatedly hidden or shown.
+A fresh publishable conversion reveals hidden generated C automatically.
+Transpilation Details returns as a resizable lower inspector opening at 38
+percent of the available workspace instead of replacing the editors.
+
+Replaced runtime SVG resources with 495 packaged PNG assets: 55 established
+glyphs at nine resolutions from 16 through 256 pixels. Ting feedback now has
+wide, labeled previous/next agent controls plus a live graphical Flow Map of the
+source-free evidence fan-out, six current agent decisions, and advisory-only
+fan-in. About now presents a 42-pixel brand mark, a fixed-size surface with a
+titlebar-blended live world UTC clock, converter identities, full workspace
+state topology, and authenticated Ting engine, registry, agent, rule, and test
+telemetry.
+
+Advanced the package to 1.0.5, the workspace contract to 0.8, the action
+registry to 0.6, and the visual system to 0.5. Converter schemas, rules,
+renderer, generated C, and Ting shadow authority remain unchanged at 0.16.0.
+
+Corrected the final physical-Windows dialog review without changing the shared
+hover design. Help, About, Ting Agent Feedback, and Ting Agent Flow Map now
+open and reopen with focus in their content, matching the Open Python dialog.
+Their maximize and close controls therefore illuminate only while genuinely
+hovered or deliberately keyboard-focused instead of retaining a blue or red
+focus line on activation. All other dialogs and converter behavior are
+unchanged.
+
+## 1.0.4 — PyPI publication refresh
+
+Reissued the fully validated 1.0.3 package under a fresh public version for a
+clean PyPI upload. The two README screenshots retain their fixed, versioned
+Cloudinary PNG delivery URLs.
+
+Advanced the package and application version to 1.0.4. Converter behavior,
+generated C, Ting agents and authority, the notification correction, workspace
+behavior, and all UI and dialog presentation remain unchanged from 1.0.3.
+
+## 1.0.3 — Reliable PyPI screenshot delivery
+
+Replaced the two unreliable public README image addresses with fixed,
+versioned Cloudinary PNG delivery URLs. Both remote objects were independently
+retrieved as 1920 × 1080 PNG files and matched the packaged screenshots byte
+for byte before the release was built.
+
+Advanced the package and application version to 1.0.3. The converter, generated
+C, Ting agents and authority, notification fix, workspace, and every other UI
+or dialog behavior remain unchanged from 1.0.2.
+
+## 1.0.2 — Focused presentation and notification polish
+
+Replaced the former release-contract-heavy README with a shorter public guide
+centered on PyCForge's purpose, installation, upgrades, immediate desktop
+launch, principal workspace features, Ting agent integration, built-in Help,
+CLI/API access, and safety boundary. Added current full-workspace and Ting
+feedback screenshots to the source distribution and PyPI description.
+
+Made the top notification banner's SVG close control follow the active
+information, success, warning, or error foreground color. Hover, focus, and
+pressed states retain the same semantic background and border family, so the
+control no longer appears detached from its message. No other workspace or
+dialog presentation was changed.
+
+Advanced the package and application version to 1.0.2. Converter schemas,
+lowering, generated-C behavior, Ting shadow authority, workspace contracts,
+and the authenticated 1.0.1 fixed-set rules remain unchanged.
+
+## 1.0.1 — Fixed sets and professional workspace continuity
+
+Added a fail-closed fixed-set profile to the active Phase 16 base. Direct
+function-local literals of 1–64 unique homogeneous integer, finite-float, or
+Boolean elements lower to read-only automatic C arrays. Exact-representation
+`in` and `not in` evaluate their searched expression once and use bounded
+linear equality. New authenticated membership facts, 1.0.1 rule identities,
+independent validation, conversion summary records, exact diagnostics, and
+positive/negative tests cover declaration and lowering. Unsupported order,
+hash-table, mutation, alias, and escape behavior remains outside the contract.
+
+Added parser-authenticated Python function folding, Fold All and Unfold All
+source controls, and subtle Python-only indent guides. Generated C remains a
+plain immutable inspection surface. Large-source fold discovery now consumes
+the existing authenticated background structure result; Fold All returns to
+the event loop immediately and applies bounded regions only after exact
+document/revision validation. Fold application touches only changed bounded
+block lines, preventing the synchronous parser/block-scan freeze reported on
+Windows.
+
+Removed the desktop shell's synthetic permanent first document. A new window
+may be genuinely empty; the first opened or created Python module becomes
+primary automatically, and every tab—including the first or final restored
+tab—can be closed. Closing the final tab persists an intentionally empty
+restart session. Linked files that remain open at exit still reopen in their
+prior order with the prior active file selected. Added an independent
+**Clear Recent Files** action that never closes tabs, deletes files, or changes
+the restart session. Long main-window titles now elide before the window
+controls, and Find/Replace keeps Previous and Next in one compact group.
+
+Replaced native dialog titlebars with reusable accessible PyCForge frameless
+chrome across Help, About, startup, settings, file browsers, command palette,
+go-to-line, guarded choices, restoration reporting, and Ting feedback. The
+flat titlebar carries the canonical brand mark and an extensible icon-toolbar
+host; resizable dialogs expose system and bounded manual resize paths.
+
+Persisted the ordered set of linked saved Python files and active linked file.
+Startup restores them sequentially under the 64-document ceiling and reports
+every unavailable or unreadable path in a nonblocking selectable dialog.
+Unsaved source text is not serialized.
+
+Added a source-free, read-only Ting feedback terminal after converted and
+rejected decisions. An overview and all six mandatory agent tabs expose exact
+evidence, gaps, bounded matching metrics, and rulepack identities. The shadow
+review has no authority over conversion and does not fabricate compiler or
+differential evidence.
+
+Updated all fourteen classified offline HTML Help pages and navigation search
+metadata needed for the new conversion and workspace features. Advanced the
+package and application identity to 1.0.1 while retaining the documented Phase
+16 base schemas and renderer.
+
+Corrected the 1.0.1 desktop presentation after physical-review feedback.
+Python source now defaults to 14 pt, generated C to 12 pt, Help body text to
+12 pt, and application controls to a 12 pt minimum. Presentation-settings
+schema 3 removes the faulty schema-2 global-font projection and oversized
+restored geometry while preserving compatible session data. Top-level windows
+fit the current monitor work area under Windows display scaling. Function fold
+markers are larger, Fold All and Unfold All are direct Edit-menu actions, the
+Ting/About status buttons are matched and contained, menu-item hover tooltips
+are disabled, and ordinary typing no longer rewrites the persistent status
+message.
+
+Completed a second physical-Windows typography correction without changing
+the editor sizes or Help article typography. Ordinary non-editor controls now
+use the exact menu font, including Help controls, file browsers, inspectors,
+About, startup, and monospaced Ting feedback. The three workspace caption
+bands use a deliberate compact 10 pt hierarchy and the Python header gives
+adaptive space to both module identity and path text. The Open preview is decoupled
+from the 14 pt source editor and uses compact menu-sized page geometry.
+Transpilation Details always starts hidden and opens as a full-height review
+mode instead of compressing the editor. Source/mapping activation returns to
+the editor. Accepted code-font choices use a durable restart mirror; guarded
+Save/Discard focus borders retain bottom clearance; QAction status tips cannot
+enter the status bar. Help, About, and startup rasterize the
+redesigned flat `brand-mark.svg` directly at the final logical size and device
+pixel ratio, eliminating enlarged 24-pixel bitmap intermediates.
+
+## 0.16.3 — Complete in-app Help and workspace usability
+
+Status: PyCForge 0.16.3 package release; active converter, rule-set, renderer,
+runtime-policy, plan, C-IR, artifact, summary, trace, and result-envelope
+contracts remain unchanged from the PyPI 0.16.2 package.
+
+Added a professional, fully offline HTML Help dialog under the new **Help**
+menu and **F1**. Fourteen editable HTML pages are classified through a
+validated catalog, presented with persistent left navigation, and searched as
+one global documentation set. They cover the entire cumulative conversion
+surface, including typed functions, expressions,
+conditionals, scalar scope publication, loops and loop `else`, containers,
+records, direct/keyword calls, explicit module imports, bounded UTF-8 file
+reading and writing, the generated-C file ABI and status codes, CLI/API use,
+diagnostics, safety, limits, shortcuts, and active identities. The installed
+application no longer relies on a PDF or an external repository for user help.
+
+Replaced editor-only font sizing with one persisted 8–32 point workspace text
+size. Direct **View** actions and `Ctrl+=`, `Ctrl+-`, and `Ctrl+0` now resize
+menus, toolbars, dialogs, trees, diagnostics, Python, generated C, previews,
+and Help together. Schema-1 editor preferences migrate into the application-
+wide setting and changes synchronize immediately.
+
+The custom Open/Save dialogs now remember per-mode geometry, columns,
+directory, and—where applicable—the browser/preview splitter and last selected
+Python file. Open never displays a restored preview unless its tree row is
+visibly selected. The first **New Module** reuses a pristine initial `main.py`
+placeholder, eliminating the accidental empty-main diagnostic while retaining
+the converter's deliberate rejection of genuinely empty bundle modules.
+
+Added Undo, Redo, Cut, Copy, and Paste to the main toolbar; enlarged module-tab
+close targets; rebuilt status-bar ownership so left feedback stretches inside
+the bar and right-side controls remain contained; and replaced stylesheet and
+editor-rail gradients/texture backgrounds with a flat blackened-steel palette.
+
+Package metadata now identifies PyPI as the authoritative distribution page.
+The package version advances to 0.16.3 because published PyPI files are
+immutable; the active converter contract remains exactly 0.16.0.
+Workspace, action-registry, and visual-system presentation identities advance
+to `pycforge-workspace/0.7`, `pycforge.action-registry/0.4`, and
+`pycforge.visual-system/0.4`; persisted presentation settings advance to schema
+`2` with bounded schema-1 font migration.
+
+Added six deterministic Ting shadow-review agents for syntax, semantics,
+ownership, lowering, verification, and typed capability/resource binding.
+Their 34 embedded tests run without skips through a read-only source gate.
+Proof-preserving pruning evaluates every registered role while using bounded
+schema and equality indexes inside each rulepack. PyCForge ships only a
+private execution runtime, authenticated registry, and precompiled Compact-IR.
+The runtime retains the bounded `.ting` Compact-IR loader/parser and verifier.
+Only the authoring-side RuleSpec source parser, compiler, writers, builders,
+consoles, reference engine, history subsystem, and command entry points are
+excluded from both public archives and retained separately under compiler
+custody.
+
+Added an accessible branded startup progress dialog driven only by completed
+initialization work. It validates the vector catalogue, all offline Help
+sources, and every packaged `.ting` artifact before constructing the
+workspace. The dialog supports safe-boundary cancellation, presents bounded
+startup errors, performs no network access, and uses the same flat visual
+surface and canonical brand mark as the main window, Help, and About.
+
+## 0.16.2 — Evaluation hardening and motionless editing
+
+Status: PyCForge 0.16.2 package release; active converter contracts,
+generated-C identities, and the 0.16.0 Programmer's Conversion Guide remain
+unchanged.
+
+Repaired the frontend's virtual-EOF coordinate mapping so valid source converts
+without a terminal newline or completely empty final line. The repair maps the
+tokenizer's virtual final position to exact EOF without inserting or
+normalizing text and preserves source bytes, newline records, document identity,
+and authenticated hash. The `clamp` reproduction no longer falls through to
+`PYC9001`.
+
+Made normal typing visually motionless across the toolbar Convert action,
+conversion-status labels, the generated-C stale/last-complete label, and Python
+source breadcrumbs. State updates now occur in place, while progress animation
+is limited to actual conversion work. Corrected Python-editor point-size loading
+so the chosen value survives restart and applies to both current and future
+split source panes.
+
+Added a compact, menu-preserving frameless shell and reduced toolbar and notice
+height without shrinking their established text. Replaced native tree icons
+with PyCForge dark-theme iconography, bounded the Open dialog's initial height,
+and moved Previous/Next navigation above the preview page. Reworked About into
+a wider categorized view with version and contract information, end-of-file and
+current/stale-state explanations, Details and split-view cues, and no
+personal-name text. The existing toolbar action remains the single Show/Hide
+control for Transpilation Details.
+
+Documented fresh and explicit-upgrade commands for both POSIX environments and
+the Windows `py` launcher. Package version 0.16.2 retains the 0.16.0 converter,
+rule-set, renderer, runtime-policy, plan, C IR, generated-artifact, summary, and
+decision-trace identities; workspace and settings identities also remain
+unchanged.
+
+## 0.16.1 — ForgeLens and blackened-steel workspace
+
+Status: PyCForge 0.16.1 release; converter contracts, generated C, and the
+0.16.0 Programmer's Conversion Guide remain unchanged.
+
+Added optional, default-on ForgeLens cross-highlighting from authenticated
+Python↔C mappings. It follows exact focused selections without taking focus or
+switching documents, persists its Editor Settings toggle, clears safely across
+document and lifecycle changes, and fails closed on excessive mapping fanout.
+Position indexing now handles Qt newline normalization, query scans stop as
+soon as their ordered interval cannot match, endpoint storage is compact, and
+unchanged marker projections are not repainted.
+
+Introduced a coordinated blackened brushed-steel workspace with restrained
+focus and selection colors, semantic primary/danger states, coherent menus and
+dialogs, and the PyCForge brand mark in About. Replaced native file pickers
+with bounded custom browsers: Open renders readable Python pages in memory with
+Previous/Next controls, while Save remains preview-free. Hardened dialog error
+recovery, path elision, accessibility descriptions, tree sizing, and preview
+retirement behavior.
+
+Added the concise five-feature UI roadmap and refreshed the public README with
+an immutable, code-rich 1600×1000 workspace screenshot. The complete package
+still uses the active Phase 16 converter identities at 0.16.0.
+
+## 0.16.0 — Scope, loop completion, and bounded UTF-8 file I/O
+
+Status: PyCForge 0.16.0 release; explicit Phase 14A-14D requests and all
+historical 0.15.3 workspace custody remain preserved.
+
+### Selective scalar scope lifetimes
+
+Added immutable, resource-bounded, independently reconstructed
+`fact-table/0.16-scope-lifetimes` proof. Scalar locals first assigned in
+exhaustive conditional branches can now lower to one uninitialized C
+function-entry declaration plus source-ordered branch assignments when every
+reachable continuation proves initialization before use. Nested conditionals
+and the surviving branch after a sibling return are reachability-aware.
+
+The profile remains deliberately selective: loops, containers, records,
+closures, globals/nonlocals, missing branch coverage, read-before-definition,
+unknown or incompatible categories, and malformed or over-budget evidence fail
+closed. Already-supported unrelated constructs remain independent.
+
+### Loop completion and safe `range`
+
+Added exact Python `else` behavior for admitted `while`, positional-`range`,
+and fixed list/tuple/dictionary loops. Natural completion and zero iterations
+run the else suite; only a source `break` owned by that loop suppresses it.
+Nested breaks do not suppress an outer else, `continue` preserves completion,
+and `return` bypasses it. One deterministic Boolean flag is emitted only when
+the loop owns a break, with clears immediately before those exact breaks.
+
+Added a structured pre-addition guard for signed-64 range induction. An update
+that would cross `INT64_MAX` or `INT64_MIN` selects the staged stop value
+instead, preserving exhaustion without undefined C signed overflow.
+
+### Closed bounded UTF-8 file profile
+
+Added one exact direct function-body context profile:
+`with open(path, "r" or "w", encoding="utf-8", newline="") as fresh_handle`
+with one direct read transfer or one direct write of an already-proved string
+name or string literal whose count is discarded. Effectful write expressions
+reject with `PYC3905` because helper-internal open cannot preserve context-entry
+before body-evaluation order.
+Reads default to 1,048,576 bytes, have a hard 16,777,216-byte ceiling, reject
+embedded NUL and non-RFC-3629 UTF-8, close exactly once, and transfer ownership
+only after successful close. Writes use borrowed text, require an exact byte
+count, close exactly once, and propagate failure. Handle aliasing, rebinding,
+escape, post-region use, explicit close, unsupported open shapes, and source
+calls into file-effect functions reject with the `PYC3901`–`PYC3908` family.
+
+Registered helpers are `pycf.file.read_all_utf8_bounded@1.0.0` and
+`pycf.file.write_utf8_exact@1.0.0`, with registry-closed transitive UTF-8
+validation. Generated file-effect entry points receive a hidden final,
+required non-null `int64_t *` status parameter in caller-owned storage. Stable
+codes are 0 success, 1 open, 2 allocation, 3 read, 4 limit, 5 embedded NUL,
+6 invalid UTF-8, 7 close, and 8 write. A successful read returns a unique
+caller-owned `malloc` buffer that the external caller must `free`.
+Every file-effect entry point null-checks its status pointer and then initializes
+it to success before any source-controlled early return or evaluation; helper
+failures overwrite that value with their stable code.
+
+Recorded the external C-string preconditions explicitly: paths must be
+non-null, NUL-terminated valid UTF-8; borrowed write text has the same
+preconditions and no embedded NUL. The helpers do not runtime-validate pointer
+validity, path UTF-8/NUL properties, or hidden write bytes after the first
+terminator. Compile-time path/write literals containing NUL reject with
+`PYC3903`/`PYC3905`; read-content statuses 5 and 6 do not claim input-string
+validation.
+
+### Contracts and custody
+
+Advanced the active converter to `0.16.0` with
+`phase16-scope-loop-file-v0.16.0`, `c-renderer-v0.16.0`,
+`conversion-plan/0.16.0`, `c-ir/0.16.0`, `generated-c/0.16.0`, and matching
+0.16.0 summary/trace identities. The result envelope remains `0.5`. Phase 16
+adds closed structured pointer, cast, conditional-expression, null, and C
+library-intrinsic C IR forms needed by the proved runtime. Historical Phase 14D
+schemas, rendering, diagnostics, output bytes, hashes, rejections, and helper
+manifests remain unchanged under explicit `0.14.3` requests.
+
+Conversion never executes source Python and never opens a path selected by the
+source. PyCForge never compiles, links, loads, or runs generated C. File I/O,
+status writes, allocation, ownership transfer, and caller `free` occur only if
+an external party separately builds and runs the generated C.
+
+The authenticated desktop worker protocol is now
+`pycforge.worker-protocol/0.2`; it preserves the active runtime-policy identity
+and all expanded resource fields across the GUI process boundary. Added a
+reproducible 35-page 0.16.0 Programmer's Conversion Guide with 22 live-converter
+examples, deterministic PDF reconstruction, and release-asset verification.
+
+## 0.15.3 — Workspace usability and PySide6 transition
+
+Status: release candidate; converter semantics remain sealed at `0.14.3`.
+
+Migrated the desktop application from PyQt5/Qt 5 to PySide6/Qt 6 and made
+`PySide6>=6.8,<7` the single required GUI binding. Updated native actions,
+signals, dialogs, input events, high-DPI behavior, CI, packaging checks, and
+clean-install smoke coverage for Qt 6.
+
+Added a bounded, persisted **Edit → Editor Settings…** control for the text
+size of both synchronized Python source views. The setting accepts 8–48 points,
+updates tab stops and editor side areas immediately, survives shared-document
+rebinding, and leaves the generated-C viewer unchanged.
+
+Added undoable Python auto-indentation on Enter. Existing leading whitespace
+is preserved and genuine suite-opening colons add four spaces; colons inside
+strings, comments, and open bracket expressions do not trigger an extra level.
+
+Removed passive source-mapping backgrounds and underlines from generated C.
+Mapping records, the overview rail, activation, and source/output navigation
+remain available, while the generated-C text surface remains read-only and
+explicit-save-only.
+
+Advanced the workspace contract to `pycforge-workspace/0.6`, the action
+registry to `pycforge.action-registry/0.3`, and the visual system to
+`pycforge.visual-system/0.3`. Presentation settings remain schema `1`, the
+worker protocol remains `pycforge.worker-protocol/0.1`, and the complete
+converter subtree remains unchanged at `0.14.3`.
+
+## 0.15.2 — Phase 15C IDE-grade authoring and inspection workspace
+
+Status: promoted and sealed; Phase 15D remains unopened.
+
+Prepared the first public PyPI distribution without changing the
+converter contract. PyQt5 is now a mandatory runtime dependency of the base
+package, so an ordinary `pip install pycforge` installs the desktop application
+and both `pycforge` and `pycforge-workspace` entry points. Removed the obsolete
+`workspace` extra, added PyPI long-description and project metadata, corrected
+the command-line examples, and added clean-build, clean-install, offscreen Qt,
+release-artifact and Trusted Publishing gates.
+
+Established the public source license as `GPL-3.0-only`, compatible with the
+GPL PyPI distribution of PyQt5, and included the complete license text in the
+source and package metadata.
+
+Advanced the package to `0.15.2`, the workspace contract to
+`pycforge-workspace/0.5`, the action registry to
+`pycforge.action-registry/0.2`, and the visual system to
+`pycforge.visual-system/0.2`. The converter remains sealed at `0.14.3`, the
+worker protocol remains `pycforge.worker-protocol/0.1`, and presentation
+settings remain schema `1`.
+
+Added identifier-only document-tab and split-pane session state, with at most
+two synchronized Python source panes. Added bounded undoable source operations
+for line duplication, line movement, indentation, outdentation, and Python
+comment toggling, together with go-to-line, whitespace visibility, and source
+fold controls.
+
+Added cancellable latest-wins source-structure analysis for already-open Python
+text. The normalized outline and breadcrumb projection is parent-linked and
+bounded by symbol count, depth, name length, and source-text budgets. Invalid
+syntax remains inert and cannot retire valid structure for unrelated open
+documents.
+
+Added deterministic literal bundle search across the explicit open
+`SourceBundle`, with immutable path-free requests, exact Python and UTF-16
+positions, bounded previews, a global 5,000-match cap, and stale-generation
+suppression. No host directory or project discovery was introduced.
+
+Added a bounded command palette that projects enabled and visible static
+registry actions without retaining handlers or adding a free-form command
+execution surface. Added payload-free session transpilation history capped at
+64 terminal records.
+
+Expanded the declarative command system to 48 actions, five persistent main
+menus, and eleven context surfaces. Added the Navigate menu, source-authoring
+commands, document-tab, bundle-search, history, text-input, and read-only-text
+contexts while preserving the exact read-only generated-C command allowlist and
+single-owner persistent `QAction` construction.
+
+Expanded the vector catalogue from 41 to 55 safe SVG icons and extended the
+shared workspace stylesheet for document tabs, split views, breadcrumbs,
+outline, bundle-search results, history, and command-palette presentation.
+
+Preserved the Phase 15A spawned-worker model, one-active/one-latest scheduling,
+bounded cancellation, immutable revision and fingerprint authentication,
+stale-result suppression, off-GUI file and search work, and incremental
+generated-C projection. Python remains the only editable code surface.
+
+Recorded current-release real PyQt evidence on the offscreen QPA backend
+using Python 3.12.13, PyQt 5.15.11, Qt build 5.15.14, and Qt runtime 5.15.19.
+One `QApplication` ran 18 focused workspace cases with zero failures, errors,
+or skips. A 250,113-character source constructed the window in 0.054 seconds,
+reached the first event turn in 0.0103 seconds, and produced 110 timer ticks at
+0.01-second intervals during 1.201 seconds of isolated transpilation. Large-file
+mode detached the syntax highlighter while preserving the shared editor buffer;
+shutdown left zero new PyCForge threads and zero worker leaks. A small
+end-to-end workspace conversion completed in 0.408 seconds as supporting
+evidence.
+
+Authenticated, assigned the canonical validation report and release
+fingerprint, and built and validated the Phase 15C milestone source archive,
+pure-Python wheel, handoff, package report, and checksum records. These
+artifacts establish Phase 15C release custody, not the wider Phase 15D
+distribution and platform gate.
+
+PyCForge remains a deterministic Python-to-C source transpiler. It does not
+compile, assemble, link, load, run, execute, debug, profile, deploy, or invoke
+generated C or a C toolchain.
+
+The real offscreen widget evidence is not visible-platform certification.
+Visible Windows 11/Linux rendering, physical display scaling, and
+assistive-technology validation remain Phase 15D gates.
+
+## 0.15.1 — Phase 15B application shell and visual system
+
+Status: implemented and validated within the available supporting scope.
+
+Advanced the workspace contract to `pycforge-workspace/0.4` and introduced the
+import-safe `pycforge.action-registry/0.1`. Every persistent application command
+now has one declarative authority for its stable ID, label, mnemonic, SVG icon,
+shortcut, tooltip, status explanation, accessible name, checkability, tone, and
+allowed surfaces. The Qt adapter creates each persistent `QAction` once and
+shares it across menus, toolbars, context surfaces, and bounded dynamic entries.
+
+Added custom gradient/icon File, Edit, View, and Transpile menus and declared
+context menus for Python source, read-only generated C, the Source Bundle
+navigator, diagnostics, mappings, conversion summary, decision trace, and
+telemetry. The custom presentation remains native-backed by `QMenu` and
+`QAction`, preserving keyboard traversal, mnemonics, shortcut columns, checked
+state, focus return, Escape dismissal, assistive exposure, submenu behavior,
+and screen-edge placement. Generated C uses an explicit read-only command
+allowlist.
+
+Introduced `pycforge.visual-system/0.1` with cohesive semantic graphite
+surfaces, layered gradients, high-contrast text, blue and violet focus accents,
+a restrained warm transpilation accent, and explicit success, warning, error,
+and danger treatments. Expanded professional self-contained SVG iconography
+uses logical dimensions and excludes raster payloads, embedded data, remote
+references, fixed physical sizing, scripts, and font-glyph dependencies.
+
+Added high-DPI and accessibility foundations: high-DPI scaling before
+application construction, logical icon sizing, stable menu accessible names,
+visible tooltips and accessible names for icon-only controls, visible keyboard
+focus, and non-color-only state treatment. The interface has no animation and
+is reduced-motion safe by construction.
+
+Removed the legacy presentation-namespace migration and compatibility surface.
+Current source, settings, menus, toolbars, tests, evidence, and distribution
+use PyCForge identity exclusively. Original pre-migration bytes remain
+authoritative in the authenticated Phase 15A archive.
+
+Preserved all Phase 15A responsiveness and isolation guarantees: spawned
+conversion, one-active/one-latest scheduling, cooperative and hard
+cancellation, immutable revision authentication, stale-result suppression,
+off-GUI file I/O and search, bounded editor projections, incremental generated-C
+population, and exact Save C authority.
+
+Bounded the structured detail inspectors with an iterative cycle-safe
+projection limited to 1,024 nodes, 16 levels, 256 children per container, and
+2,048 characters per value. Corrected scroll-area context placement, made
+uncommitted identity edits immediately stale and unsavable as C, and suppressed
+cancellation-pending diagnostics as non-current.
+
+Hardened release custody around a descriptor-bound, size-bounded source
+snapshot and a validation-subject digest that is checked against the exact
+packaged bytes. Packaging now pins its production environment, compares
+duplicate wheel and normalized-source builds, inspects and smokes the sealed
+wheel payload, rejects noncanonical validation JSON, and durably publishes the
+seven-artifact directory only after the final vocabulary and checksum graph
+passes.
+
+The package is `0.15.1`; the converter remains sealed at `0.14.3`, the worker
+protocol remains `pycforge.worker-protocol/0.1`, and presentation settings
+remain schema `1`. PyCForge remains a deterministic Python-to-C source
+transpiler. No C compiler, linker, loader, runtime execution, debugger,
+terminal, toolchain, project explorer, plugin system, or generated-C editor was
+added.
+
+PyQt5 is unavailable on the validation host, so Phase 15B evidence is
+supporting source, static, headless, registry, icon, and optional-widget
+evidence only. Visible Windows 11/Linux rendering, real display scaling, and
+assistive-technology validation remain Phase 15D gates. Phase 15C and Phase 15D
+remain unopened.
+
+Final discovery runs 750 tests: 734 pass, 16 are expected skips, and none fail.
+Eleven skips require unavailable PyQt5 widgets; five require unavailable older
+optional custody artifacts.
+
+## 0.15.0 — Phase 15A responsiveness and isolation
+
+Status: promoted and sealed.
+
+Replaced workspace in-process conversion with a spawn-only process supervisor.
+The bounded `pycforge.worker-protocol/0.1` uses canonical JSON over byte-only
+connections and validates generation, bundle, transport, request, artifact,
+mapping, and output identities before publication. Scheduling is exactly one
+active plus one replaceable latest pending request.
+
+Added cooperative cancellation with a 750 ms grace, hard termination and
+two-second reclamation, latest-pending start bounds, non-blocking close, and
+recoverable startup, crash, malformed/oversized IPC, broken-pipe, and worker
+resource-exhaustion handling. Canceled, failed, stale, superseded, partial, or
+mismatched work cannot publish C or replace last-known-good C.
+
+Added immutable off-GUI revision/index services with cached UTF-8 and UTF-16
+position facts. Convert and Save C remain disabled until the latest revision
+authenticates. Moved linked-file reads, hashes, observations, and guarded atomic
+writes to bounded daemon workers; an in-flight stale Save C fails before atomic
+replacement.
+
+Added debounced latest-wins literal search with an exact total and a 5,000-range
+projection cap. Added automatic large-file editor mode, bounded syntax/bracket
+work, marker and overview caps, viewport-focused selections, incremental 32 KiB
+generated-C projection, and deferred hidden output/detail work. Source edits
+are coalesced before proportional controller synchronization.
+
+Validated direct-versus-isolated serialized-result equality, hard-cancel and
+failure containment, maximum-envelope revision/search/index behavior, injected
+slow file I/O, and 100 edit/convert/cancel cycles without stale publication,
+deadlock, crash, obsolete pending work, or orphan processes.
+
+Advanced the package to `0.15.0` and workspace contract to
+`pycforge-workspace/0.3`. The complete converter subtree and every converter
+contract remain sealed at `0.14.3`.
+
+PyCForge remains a Python-to-C source transpiler. No compiler, linker, loader,
+generated-C executor, runner, debugger, terminal, toolchain, plugin,
+project-explorer, host-discovery, or generated-C editor was added. Phase 15B,
+15C, and 15D remain unopened; visible Windows 11/Linux PyQt and accessibility
+claims are reserved for Phase 15D.
+
+## 0.14.4 — Hardening Checkpoint E
+
+Status: promoted and sealed.
+
+Completed the roadmap's post-Phase-14 full-subset architecture review,
+deterministic full-supported-subset fuzz and metamorphic gate, and documentation
+and 69-entry feature-matrix reconciliation. No Python construct, C IR shape,
+helper, diagnostic, conversion policy, public converter schema, or generated-C
+style was added or changed.
+
+Separated the package identity (`0.14.4`) from the sealed deterministic
+converter contract identity (`0.14.3`). Golden output, serialized results,
+facts, RulePlans, summaries, traces, telemetry, diagnostics, mappings, and
+fingerprints remain Phase 14D values.
+
+Corrected the active desktop identity to PyCForge across front-facing titles,
+accessibility names, theme exports, and the settings namespace. Added a bounded,
+non-destructive migration for allow-listed predecessor presentation settings
+and retained non-exported compatibility aliases only for sealed historical
+validators.
+
+Established `pycforge-workspace/0.2` and a binding workspace-quality addendum.
+The addendum assigns the requested process-isolated conversion supervisor,
+maximum-input responsiveness, professional IDE-grade authoring and inspection,
+custom gradient/icon main and context menus, accessibility, high-DPI, and real
+Windows 11/Linux PyQt gates to Phase 15. Checkpoint E does not claim those
+future gates or open Phase 15.
+
+PyCForge remains a Python-to-C source transpiler. It does not compile, link,
+load, run, execute, debug, benchmark, or otherwise invoke generated C or a C
+toolchain.
+
+Promotion executes all 69 frozen feature-matrix entries plus the unlisted
+default, with 37 supported witnesses converted and 33 boundary witnesses
+rejected without mismatch. The seeded hardening corpus contains 16 fixed and
+64 generated cases, four per promoted family, and all 80 match the
+authenticated Phase 14D predecessor byte-for-byte.
+
+Final validation discovers 589 tests: 572 pass, 17 are expected skips, and
+zero fail. The focused Checkpoint E set passes 46 of 46, and every cumulative
+source-only audit passes. Reproducible wheel and normalized source-archive
+builds are byte-identical; isolated wheel and extracted-source smokes pass.
+The wheel contains both PyCForge entry points, exactly 17 SVG assets, and no
+native binaries.
+
+## 0.14.3 — Phase 14D exact required keyword-only calls
+
+Status: promoted and sealed.
+
+Added one exact source-only declaration and call profile for required
+keyword-only parameters on already-resolved direct source functions. An admitted
+function may have existing required positional-only and positional-or-keyword
+parameters followed by one or more exactly annotated required keyword-only
+parameters. Every `kw_defaults` entry is null; positional defaults,
+keyword-only defaults, `*args`, and `**kwargs` remain rejected.
+
+Ordinary positional actuals bind only positional-capable formals. Explicit named
+actuals may bind unbound positional-or-keyword or required keyword-only formals.
+Every required formal is covered exactly once with an exact category and
+representation match. Explicit values stage once in Python source order; only
+pure temporary references are arranged in full formal order for the existing
+structured `CCallExpr`. No runtime binder, `TypeError` channel, default
+evaluation, coercion, allocation, ownership transfer, or cleanup model was
+added.
+
+Added complete positive and negative `keyword-only-call-binding-facts` under
+`fact-table/0.14.3` and the helper-free
+`phase14.keyword_only_call.exact_binding@0.14.3` RulePlan. The lowering shape is
+`source-order-actual-temporaries-formal-order-references-v1`. Independent
+validation reconstructs declaration kind, target, name binding, coverage,
+categories, source/formal orders, C parameter order, and exact plan
+correspondence before lowering.
+Required-keyword-only declarations remain in the existing function-signature
+facts without changing the serialized `ParameterFact` shape. Affected existing
+`FunctionDef` RulePlans gain explicit keyword-only parameter and
+C-interface-mode-erasure facts and obligations, and independent validation
+covers admitted declarations even when they have no call site.
+
+No new source diagnostic code is required. `PYC2904` retains missing coverage
+and excess positional arity, `PYC2905` exact representation mismatch, `PYC2910`
+unpacking and excluded call shapes, and `PYC2912` exact name-binding failures.
+Under active 0.14.3 identities `PYC2911` continues to reject defaults,
+defaulted keyword-only parameters, variadics, and keyword-only declarations
+outside the exact required profile; it no longer rejects an otherwise eligible
+required keyword-only declaration solely because `kwonlyargs` is nonempty.
+Historical 0.14.2 diagnostics remain unchanged.
+
+Advanced the active rule set to
+`phase14-required-keyword-only-calls-v0.14.3`, renderer to
+`c-renderer-v0.14.3`, and conversion-plan, C IR, generated-C, summary, and
+decision-trace envelopes to 0.14.3. SourceBundle 0.2, Python IR 0.4, result
+serialization 0.5, target and semantic policies, the helper registry, and all
+container/module/record/numeric/conditional policies remain frozen.
+
+Explicit 0.14.2 and earlier requests retain their exact facts, plans,
+diagnostics, generated-C bytes, and fingerprints. Under active 0.14.3
+identities, sources selecting no Phase 14D declaration or call behavior retain
+Phase 14C generated-C bytes and output fingerprints. Required keyword-only
+support adds no C IR syntax kind, renderer grammar, helper, host discovery, or
+toolchain surface. Generated C remains source-validated only and is not
+compiled, linked, loaded, or executed. Defaults, variadics, unpacking, dynamic
+targets, methods, recursion, exceptions, closures, generators, async behavior,
+and every neighboring Phase 14 family remain excluded. Phase 15 has not
+started.
+
+Promotion passed 539 discovered tests: 524 passed, 15 skipped, and zero failed.
+The skips are exactly 10 for unavailable PyQt5 and five for unavailable older
+custody artifacts. The focused Phase 14D gate passed 65 of 65 tests. Every
+active cumulative audit passed, including the required-keyword-only and
+Phase 14D transition audits.
+
+Two fixed-epoch builds produced the same 340,054-byte
+`pycforge-0.14.3-py3-none-any.whl`, SHA-256
+`c0dd0c0ed79131daa5af815a8a9bb096b9f955c9c617ec0b8eb6a10c69d27b7f`.
+The wheel archive and `RECORD` each account for 132 members: 17 SVG assets and
+zero native-code members. Two normalized source-archive builds were likewise
+byte-identical. The promoted converter subtree SHA-256 is
+`74b32c25e40af3398dd46288941812ce7ad87f0d4b72fec3d3bd786cc1b8f3a8`.
+
+Release validation remained source-only: no gate compiled, linked, loaded, or
+executed generated C. No new actual PyQt5 widget or Windows 11 execution is
+claimed. Historical opening records remain preserved, and Phase 15 has not
+started.
+
+## 0.14.2 — Phase 14C direct exact keyword calls
+
+Status: promoted and sealed.
+
+Added one closed compile-time binding profile for explicit keyword arguments on
+already-resolved direct source-function calls. Calls may use a leading ordinary
+positional prefix followed by one or more explicit named keywords. Every
+required formal is bound exactly once, positional-only formals remain
+positional-only, and actual/formal categories must match exactly. Same-module
+and existing explicit cross-module source-function bindings are eligible;
+dynamic targets, callable values, methods, defaults, keyword-only parameters,
+variadics, `*`/`**` unpacking, recursion, `range` keywords, and record-
+constructor keywords remain excluded.
+
+Added independent keyword-call analysis and reconstruction,
+`keyword-call-binding-facts` under `fact-table/0.14.2`, and the helper-free
+`phase14.keyword_call.exact_binding@0.14.2` RulePlan. Argument values are staged
+left to right and once in Python source order, then pure temporary references
+are arranged in formal ordinal order for the existing structured `CCallExpr`.
+No C IR node kind, renderer grammar, helper, runtime binder, failure channel,
+allocation, ownership transfer, or cleanup model was added.
+
+Added `PYC2912` for exact static name-binding failures: unknown keyword names,
+positional-only names used as keywords, positional/keyword collisions, and
+duplicate keywords. `PYC2910` remains the boundary for `*`/`**`, null keyword
+names, unpacking, and other excluded keyword shapes. Existing target,
+declaration, arity, category, record, `range`, and recursion diagnostics retain
+precedence.
+
+Advanced the active rule set, renderer, conversion plan, C IR, generated-C,
+summary, and trace envelopes to 0.14.2. SourceBundle 0.2, Python IR 0.4, result
+serialization 0.5, all public policies, the helper registry, Phase 14A numeric
+facts/helpers, and Phase 14B `fact-table/0.14.1` conditional facts and RulePlans
+remain unchanged. Explicit 0.14.1 requests retain their historical keyword
+rejection and artifact behavior; active sources selecting no 14C call retain
+predecessor generated-C bytes and output fingerprints.
+
+Promotion authenticated the sealed Phase 14B source archive and wheel, passed
+the cumulative suite and audits including the keyword and Phase 14/14B/14C
+transition audits, sealed deterministic wheel and source-archive builds, and
+passed isolated package validation. All release validation remained source-only;
+generated C was not compiled, linked, loaded, or executed. PyQt5 was unavailable
+in the release environment, so no new widget execution is claimed and sealed
+offscreen-widget evidence remains preserved. Windows 11 execution is not
+claimed. Phase 14D and Phase 15 have not started.
+
+## 0.14.1 — Phase 14B conditional temporary regions
+
+Status: Phase 14B promoted and sealed.
+
+Added exact conditional placement for statement-producing temporaries belonging
+to expressions already supported by the cumulative scalar subset. Boolean
+`and`/`or` expressions now use an initialized Boolean result and flat guarded
+assignments. Later operands of chained comparisons use guarded materialization
+and rolling middle values, preserving left-to-right, exactly-once evaluation
+without eagerly evaluating skipped operands.
+
+Added independent conditional-region analysis and validation,
+`fact-table/0.14.1` conditional facts, two 0.14.1 RulePlan families, and active
+`conversion-plan/0.14.1`, `c-ir/0.14.1`, `generated-c/0.14.1`, summary, trace,
+rule-set, and renderer identities. No Python syntax, primitive operation,
+public policy, helper, runtime failure channel, allocation, ownership, cleanup,
+or C IR node kind was added.
+
+Preserved the sealed Phase 14A numeric policy and helper registry exactly.
+Explicit 0.14.0 configuration retains its historical artifacts and placement
+rejections; active sources that select no conditional region retain predecessor
+generated-C bytes and output fingerprints. General exceptions, heap objects,
+dynamic dispatch, closures, generators, async behavior, context cleanup, and
+the broader class model remain excluded.
+
+## 0.14.0 — Phase 14A bounded integer floor arithmetic
+
+Status: Phase 14A sealed.
+
+Added exact integer `//` and `%` for existing integer-like expressions when
+the divisor is a direct signed integer literal in
+`[-9223372036854775807, -2]` or `[1, 9223372036854775807]`. Zero, negative one,
+`INT64_MIN`, Boolean, floating, dynamic, folded, calculated, and out-of-range
+divisors reject deterministically.
+
+Added separate numeric analysis and lowering, `fact-table/0.14` numeric
+operation facts, the `phase14.numeric.floor_arithmetic` RulePlan family,
+`conversion-plan/0.14`, `c-ir/0.14`, `generated-c/0.14`, and 0.14 summary and
+decision-trace identities. The active numeric policy is
+`phase14-proved-floor-arithmetic-v0.14`.
+
+Activated the frozen `pycf.i64.floor_div@1.0.0` and
+`pycf.i64.floor_mod@1.0.0` Phase 10 assets without changing their registry or
+asset fingerprints. Each occurrence selects exactly one helper, and the
+registry emits each selected helper once. Deterministic signed-64 temporaries
+preserve left-to-right, exactly-once operand evaluation.
+
+The admitted divisor proof excludes C11 division by zero and
+`INT64_MIN / -1`; no runtime failure channel, exception emulation,
+arbitrary-precision runtime, allocation, or cleanup was added. Mathematical
+fixtures close Python floor quotient, divisor-sign remainder, and the division
+identity across the supported sign and boundary cases.
+
+Preserved exact explicit Phase 13 conversion behavior and the unchanged module,
+record, container, workspace, no-host-discovery, and source-only product
+boundaries. Generated C was not compiled, linked, loaded, or executed.
+
+Phase 14A is sealed independently. Broader Phase 14 remains closed pending a
+new decision and explicit approval. Phase 15 has not started.
+
+## 0.13.0 — Phase 13 static records
+
+Status: promoted.
+
+Added a deliberately narrow immutable-record subset expressed with one exact
+top-level Python class shape. Accepted records contain 1–64 ordered `int`,
+`float`, or `bool` fields, an exact structural `__init__`, direct fresh
+function-local positional construction, and direct statically resolved field
+reads.
+
+Added `fact-table/0.13` record definitions, fields, initializers, instances,
+bindings, and accesses; seven record RulePlans; `conversion-plan/0.13`; record
+nodes in `c-ir/0.13`; `generated-c/0.13`; and 0.13 summary and decision-trace
+identities. The active record policy is
+`phase13-immutable-automatic-records-v0.13`.
+
+Record lowering emits deterministic named C `typedef struct` declarations and
+fully initialized `const` aggregates in automatic function storage. Arguments
+are evaluated left to right and once before construction; field reads use
+direct member access. No record helper or runtime is selected.
+
+General methods, inheritance and the broader Python object model remain
+unsupported. Records cannot be mutated, aliased, rebound, copied, escaped,
+passed, returned, stored in containers, imported, or used across modules.
+There is no heap allocation, null state, ownership transfer, or cleanup.
+
+Adversarial hardening added binding-identity constructor resolution,
+read-after-construction and complete fresh-local proofs, dunder-field and
+annotation-builtin collision rejection, correct companion-module diagnostics,
+cooperative record cancellation, exact const/member and field-type C IR
+validation, manifest-bound provenance, and independent serialized record-fact
+cross-validation. Historical `fact-table/0.12` module records retain their
+exact shape; record linkage remains in Phase 13 evidence.
+
+An initial working candidate was abandoned when an external compile-only
+review triggered the declared no-toolchain rollback rule. The release candidate
+was reseeded from a newly authenticated 0.12.2 extraction; the incident remains
+recorded and is not rewritten as passing evidence.
+
+Preserved the Phase 12 function-import profile, Phase 11 containers, Phase 10
+helper registry, source-only product boundary, and PyCForge workspace safety
+model. Explicit historical Phase 12 requests retain their 0.12 identities, and
+class-free Phase 13 conversions preserve predecessor generated-C bytes.
+
+The sealed 0.12.2 predecessor was authenticated before Phase 13 edits. Windows
+11 laptop testing remains planned user feedback after all phases; this release
+does not claim Windows execution. Phase 14 has not started.
+
+## 0.12.2 — PyCForge workspace hardening
+
+Corrected conversion-generation retirement, Save As destination validation,
+unexpected worker failure recovery, visible module identity commits,
+document-reorder controls, Unicode replacement navigation, keyboard access,
+and failure-tolerant versioned presentation settings without changing the
+sealed Phase 12 converter.
+
+## 0.12.1 — PyCForge workspace
+
+Introduced the optional professional PyQt5 workspace over the sealed Phase 12
+converter, including explicit bundle navigation, Python and immutable C
+editors, diagnostics and mappings, stale-output protection, and atomic linked-C
+saving.
+
+## 0.12.0 — Phase 12 explicit module bundles
+
+Introduced the bounded 1–64-document SourceBundle profile, exact compile-time
+direct-function imports, deterministic dependency ordering, and one generated
+C translation unit without host module discovery or runtime initialization.