PyCForge editor fixes — 1.2.1 and 1.1.11

Use 1.2.1 to update an existing 1.2.0 installation. This preserves the optional
PCFC11 build integration. Version 1.1.11 updates the separate 1.1.10 conversion
line with its recent runtime builtins, lists, formatting, modules and file I/O.
Choose one wheel for an environment; these are separate package lines.

CONFIRMED AND FIXED

The supplied PowerShell traceback was reproduced in both original versions:
close the final Python tab while Generated C is visible following conversion.
Clearing the C pane calls the marker updater, which accessed an active document
after none remained. LookupError interrupted the UI update before clearing the
Source Bundle. The remaining row then blocked Open/New with "The selected
module no longer exists". Empty marker refresh now clears safely. Open and New
also repair a stale navigator selection against the controller's live documents.

Missing fold arrows were separately reproduced on module switches and explicit
syntax rehighlighting. Both retire the editor fold cache; previously the cached
background structure was not reinstalled. Current structure now restores the
displayed module's fold markers through tab projection and a coalesced Qt timer.
This does not synchronously parse large files on the GUI thread. Results for old
text, closed documents, or old generations are rejected.

The older 1.2 line also receives existing empty-workspace breadcrumb and Qt
buffer-lifetime protections already present in the 1.1.10 conversion line.

In 1.2.1, the PCFC11 dialog opens with keyboard focus in the compiler field,
including reopening after a title control held focus. Compiler and output
Browse buttons use the shared PyCForge custom file dialogs with no preview.
Compiler selection requires an existing file; output names are preserved
exactly, including .exe, .o and extensionless names. Existing outputs require
confirmation. Cancel preserves the previous path and choosing a path writes
nothing. The dialogs retain their custom chrome and opaque application theme.

Both branches remove the Ting Shadow / Advisory badge from About. Product
versions match the package in Qt application metadata, workspace titles,
startup, About and every Help footer. The PCFC11 report shows 1.2.1, and Help
uses the installed version in its downloaded-package example. Component
contract, schema and Ting engine versions remain their own actual identities.

VERIFICATION

Each final source build passed 37 focused lifecycle/workspace tests, including
all eight new regressions: exact visible-C close/reopen crash, repeated closing
and reopening, stale navigator recovery, tab switching in both gutters, syntax
rehighlighting, edits with obsolete structure callbacks, rejected conversion,
and late callbacks after the last module is closed. There were 174 passing
subtests for 1.2.1 and 194 for 1.1.11.

Before final consolidation, broader runs passed 224 tests / 490 subtests with
15 skips in 1.2.1 and 313 tests / 763 subtests with one skip in 1.1.11. Their only
three failed checks were the project module-size limit. Consolidating duplicate
marker clearing resolved them; the final 37-test follow-ups reran those checks.
The raw logs preserve both runs. No full converter-suite rerun is claimed.

Additional UI checks passed: 38 tests / 213 subtests in 1.2.1 and 18 tests /
204 subtests in 1.1.11. Seven new PCFC11 path/focus tests passed again against
the installed 1.2.1 wheel. These include actual modal dialogs, cancellation,
file existence, overwrite confirmation and no native QFileDialog fallback.
Installed product-version and About-label checks passed in both branches.

Both wheels were installed into separate environments. All eight new regressions
passed again against installed code. Installed startup, every Help page, actual
typed conversion, and PCFC11 dialog/entry selection passed for 1.2.1. Native
PCFC11 compilation was not run because the external compiler is unavailable.
The installed 1.1.11 startup, six Ting agents, all 21 Help pages, both conversion
modes, editor tools, and three-module native file workflow passed. Its generated
program output and file bytes matched Python and the documented example.

Converter source is byte-for-byte unchanged in each branch. The 1.2 PCFC11 build
service source is also byte-for-byte unchanged. Dependencies are unchanged.
README screenshot links and screenshot bytes are preserved, with exactly two
README links. HTML Help contains usage information, without cycle status.
Distribution checks verify wheel/source metadata, payloads, assets and licenses;
the complete ZIP files include reports, source diffs and raw regression evidence.

All automated GUI checks used Linux Qt offscreen, Python 3.12 and PySide6 6.12.
Native Windows acceptance remains pending. No PyPI publication was performed.
Incomplete/invalid Python syntax cannot provide reliable new fold boundaries;
single-line functions have nothing to hide and bounded large-file mode disables
folding. Rejection of syntactically valid Python by the converter does not by
itself disable folding.
