PyCForge 1.3.14 — HTML Help and README review

Scope
-----
Read every one of the 21 Help pages, the catalog, shared styling, Help viewer,
README, relevant converter/runtime code, and documentation verification tooling.
The existing task-first structure is sound: getting started, separate Typed and
Runtime references, operation/diagnostics, and quick reference. Preserve that
order and the five categories. Keep Help offline and the README an orientation
to the product rather than a release log or a duplicate manual.

This is a documentation release. Application metadata is 1.3.14; all converter
and native-build sources remain byte-for-byte equal to 1.3.13. Existing converter
contract identifiers intentionally remain unchanged. No dependencies were added
or pinned. Historical release reports continue to describe their own versions.

Findings and corrections
-----------------------
1. README still carried 1.3.4, excluded inheritance and Runtime sets, and described
   PCFC11 as the sole integrated compiler. Update the version and supported
   functions, closures, decorators, containers, sets, numbers, inheritance, and
   five compiler families. Preserve the structure and starter code.
2. The Help limits page still described a single-inheritance chain. State the
   complete hierarchy bound: 64 distinct user classes including the subclass,
   plus object, with 64 fields and 64 distinct user methods.
3. The class-annotation table omitted subclass acceptance. Make that explicit.
4. Workspace setup stated a Typed-only per-module function requirement without
   the Runtime exception. Distinguish the two modes at that decision point.
5. Start-page dependency prose named release families despite the unpinned
   package policy. Align it with actual metadata and startup behavior.
6. Some reference labels omitted sets; one table called super a parent lookup.
   Align labels with current coverage and describe cooperative method lookup.
7. The API page put native compilation after the footer and omitted several
   sections from its contents links. Move the footer last, group result handling
   at the end, and expose every main section in reading order. Add Compile C to
   the workspace contents links; align comprehension contents with body order.
8. Runtime standalone instructions incorrectly said PyCForge only emits C.
   Point to the optional integrated build action and keep execution separate.
9. The inheritance explanation lacked a complete cooperative-constructor diamond.
   Add one independent executable example with kwargs, shared root state, actual
   C3 call order, and an exact expected result.
10. Add targeted caveats rather than repeating every boundary as a warning.
    Seven pages receive one box each. Fourteen pages receive no caveat box.

Caveat placement and intent
--------------------------
- Variables, types, and strings: after adjust(10), explain that intermediate
  integer results must fit int64, Typed overflow is a caller responsibility,
  and float is not an arbitrary-precision substitute.
- Runtime conversion and C use: after the complete C caller, explain backing
  storage lifetime, shallow PV copies, state shared by calls in one context,
  fresh contexts for independent batches, and disposal after errors.
- Runtime strings: after split/replace/join, explain retained intermediate
  strings and why collecting fragments avoids repeated growing prefixes.
- Runtime containers: after the set/slice example, explain portable ordered
  output and meaningful Python/C comparisons for unordered sets.
- Runtime functions: after the union example, distinguish ordinary Python hints
  from PyCForge checks and explain coercion and alias-boundary consequences.
- Runtime classes: after the new diamond, explain why super reaches a sibling,
  compatible cooperative signatures, and source-controlled constructor calls.
- Runtime files: after read/process/write, explain that closure does not undo
  truncation or a partial write, and place atomic replacement with the host.

The boxes use the exact label "PyCForge caveats", a muted warm background and a
thin rectangular border. One-cell presentation tables make all four borders
render in the actual QTextBrowser, whose HTML/CSS support is narrower than a web
browser's. Text remains selectable and included in global Help search. There
are no scripts, external resources, new pages, or new dependencies in Help.

Page-by-page disposition
-----------------------
Start here: retain first conversion and installation examples; refresh feature
  orientation, dependency wording, topic labels, and a short guide to caveats.
Desktop workspace: retain editor explanations and compiler table; clarify
  module requirements and expose compilation in the contents links.
Supported conversions: retain the mode comparison; clarify exception recovery
  as outside the supported forms.
Variables, types, and strings: retain all six examples; add the integer caveat.
Branches and loops: retain examples and zero-iteration guidance; update the
  Runtime comprehension link label.
Containers and records: retain unchanged. Its Typed restrictions are explicit.
Functions and module variables: retain unchanged. Explicit supplied imports,
  per-context initialization, and mutable-global restrictions are already clear.
Reading and writing files: retain unchanged. Its status table and complete C
  caller already explain buffer ownership and partial-write failure.
Runtime conversion and C use: retain examples and error handling; add ownership
  caveat and correct compilation and cooperative-lookup wording.
Runtime strings: retain examples and Unicode details; add construction caveat.
Runtime containers: retain examples and tables; state the existing set example's
  exact output and add the ordering caveat.
Runtime classes: retain the original mixin example; add navigable lookup and
  constructor sections, one cooperative diamond, and its caveat.
Runtime functions: retain all examples, including shared/fresh defaults and
  late-binding alternatives; clarify subclass annotations and add check caveat.
Runtime comprehensions: retain examples and scope explanation; align contents
  order with body sections. Existing allocation/work-limit prose is sufficient.
Runtime file workflows: retain both standalone examples and complete report;
  add the non-transactional write caveat and correct previous-page wording.
Command line and Python API: retain all code examples; repair contents/body/
  footer ordering and keep native compilation discoverable.
Fixing conversion errors: retain diagnostic tables and example; identify C3
  failures and include the logical source file in runtime error guidance.
Conversion and input limits: correct hierarchy and closure descriptions and
  distinguish source/value/file limits from editor limits.
Understanding Ting feedback: retain unchanged. Advisory scope and missing
  evidence are already stated clearly.
Keyboard shortcuts: retain unchanged. Mode selection and Compile C are current.
Conversion checklist: retain unchanged. It already joins source preparation,
  C caller requirements, compilation, and behavior comparison in useful order.

README preservation
-------------------
183 lines, below its established 200-line limit. Same section progression,
with the existing compiler section renamed Compile C. All three Python blocks
are unchanged. Both screenshot Markdown expressions and both local image assets
are byte-for-byte unchanged. Exactly two HTTP(S) URLs remain, both the original
screenshots. No other Markdown, HTML, or reference links were added. Contact and
license orientation are preserved. The existing README hash freeze in the
verification script was replaced with the authorized current-version, length,
and screenshot-only link checks; executable-example checks remain active.

Executed validation
-------------------
- 21 Help pages / five categories loaded successfully in the actual Qt viewer.
- 56 Python Help examples compiled and matched Python behavior: 22 Typed and
  34 Runtime. All 55 original Python examples remain unchanged; one was added.
- Five Python API examples, three complete C callers, two Runtime module
  bundles, and all three README Python examples passed existing validation.
- The new diamond prints ['root', 'right=2', 'left=1'] in both Python and C.
- Existing regex-edit and formatting demonstrations passed.
- 39 focused Help, distribution, presentation, and version/contract tests passed,
  together with 351 subtests. Every Help link and fragment resolves.
- All seven boxes rendered as native one-cell rectangles with four 1px borders.
  Layout checks passed at 1220x850 and 900x680, with no horizontal overflow.
  Screenshots were visually inspected; these review images are not deliverables.
- Global search finds all seven caveat pages, plus their start-page explanation.
- The README's GCC build command passed with the installed GCC path substituted
  for its placeholder, and its generated program exited successfully.
- Preservation checks found no missing application files and no changed
  converter/build sources or dependencies. All 68 original marked Help code
  blocks (including API/module/C examples) remain unchanged.

Environment: Linux x86-64, Python 3.12.14, GCC, offscreen PySide6/Qt. This refresh
uses focused documentation and packaging validation; it does not claim a new
complete converter regression or native Windows/macOS acceptance run. The
1.3.13 converter validation remains historical evidence for unchanged code.

Reproduction
------------
From the source root:
  python tools/verify_conversion_documentation.py
  python -m pytest -q tests/test_help_documentation_0_16_3.py
  python -m pytest -q tests/test_public_distribution.py
  python -m pytest -q tests/test_release_1_0_2_presentation.py
  python -m pytest -q tests/test_checkpoint_e_versioning.py
  python -m pytest -q tests/test_release_contract_0_16_3.py

The verifier compiles and executes the reviewed documentation examples in
isolated temporary directories. It is a developer verification tool; normal
conversion never executes supplied source. Machine-readable evidence is in
evidence/documentation_1_3_14. Package verification is recorded separately in
the release ZIP's distribution-verification.json.

Primary references used to cross-check explanatory wording
---------------------------------------------------------
Python 3.12 builtins (super), typing notes, and default-argument tutorial;
Qt 6 Supported HTML Subset for native text tables and border styling:
https://docs.python.org/3.12/library/functions.html#super
https://docs.python.org/3.12/library/typing.html
https://docs.python.org/3.12/tutorial/controlflow.html#default-argument-values
https://doc.qt.io/qt-6/richtext-html-subset.html
PyCForge-specific ownership, limits and annotation claims were checked against
its own source and executable examples, not inferred from general Python docs.
