[pull] main from pineforge-4pass:main - #148

…309)

v1.0.0 (tag 5718c5d, built from main 133f571) and pineforge-codegen 1.0.0
shipped on 2026-09-30, and the hub image pineforge-release:1.0.0 carries the
pair. The pages still said "Unreleased", "main is ahead of v0.13.1",
"codegen main (not in a release yet)" and "1.0.0-rc.1". What is now true:

- CHANGELOG.md: "Unreleased" is "1.0.0 — 2026-09-30", opened by a summary:
  the first stable release under semantic versioning, engine and codegen
  on one version (engine v1.0.0 + codegen 1.0.0, hub image 1.0.0), the
  three prebuilt tarballs, v1.0.0-rc.1 (bb9ec14) and the one commit after
  it (133f571, #308: the test_adapter_lookup_index_scaling CI flake fix,
  the docs-only CI skip, the benchmark refresh; no src/, include/, cmake/,
  examples/ or CMake file changed), and that the notes below are the
  notable changes since v0.13.1. The planned-1.0 hedges are present
  tense; codegen "main branch" is 1.0.0.
- README.md: a "Prebuilt library" subsection names the v1.0.0 release and
  its three tarballs; front door 1 installs pineforge-codegen==1.0.0; the
  MCP image bundles engine v1.0.0 with codegen 1.0.0; the Releases list
  opens with v1.0.0; the scoreboard and the benchmark refresh line name
  the release (neither was re-measured on it; the releases changed no
  grade).
- docs/pages/install.md: a "Prebuilt tarballs" section (asset names,
  checksum, layout, Eigen) and the hub's engine1.0.0-codegen1.0.0 tag.
- docs/pages/integration-cmake.md: find_package pins are 1.0, and the page
  states the rule the package installs (write_basic_package_version_file,
  SameMajorVersion over MAJOR.MINOR.PATCH; FILE and git-describe versions).
- docs/pages/abi-stability.md: version.h as v1.0.0 ships it (FULL "1.0.0",
  sha 5718c5d; rc.1 reads "1.0.0-rc.1"); ABI v4 and the v19 epoch ship in
  v1.0.0.
- public-contract, live-surface, native-engine (prose), pine-to-native
  (table text), report-schema, ffi-python, examples-multi, configuration,
  mtf, tutorial-macd, tutorial/README.md, docker/README.md, docs/coverage.md,
  docs/pine_v6_audit_master.md, docs/pine_v6_coverage_detail.md: "main" /
  "not in a release yet" / "the last tagged release" become v1.0.0 or
  codegen 1.0.0; the four recorded request.* rows of the coverage detail
  are "✅ Runtime" (the legend's bucket for strategy_set_recorded_series)
  and request.footprint is "❌ Unsupported" like the footprint.* rows; the
  "Fundamentals and external data" list says 0.10.4 rejects the four and
  1.0.0 reads recorded answers.
- CHANGELOG.md: time()/time_close() with bars_back/timeframe_bars_back:
  0.10.4 accepted both arguments but ignored them and read the current
  bar's time (checked with PyPI 0.10.4: it emits
  pine_time(current_bar_.timestamp, ...)), so the note no longer says they
  were refused.
- abi-stability.md: the v18 -> v19 step (both epochs are development
  builds after v0.13.1, PF_ABI_VERSION 4 at ab9714b and fc7aad6) is the
  internal epoch transition; native-engine.md: the Coof / MagnifierCoof
  enumerators existed only in development builds (no tag has them).

Checked against the tagged trees and artifacts, not memory: VERSION at
v1.0.0 is 1.0.0; PF_ABI_VERSION 4 at v1.0.0, 3 at v0.13.1; v0.13.1 has no
native_c_api.h; codegen v1.0.0 (5bf595b) differs from 70c2b4af only in
docstrings and metadata, attaches the Pine adapter, lowers varip, imports,
foreign request.security and the recorded requests, and has no CLI; the
three tarballs pass their .sha256 and hold lib/, include/pineforge/ and
lib/cmake/PineForge/; codegen 1.0.0 from PyPI plus the macOS tarball runs
front door 1 (50 trades, net 569.97) and 0.10.4's output fails to compile
against v1.0.0; find_package 1.0 / 1 / 1.0.0 EXACT find the tarball and
0.13 / 0.14 / 1.1 / 2.0 do not; the hub 1.0.0 image prints the documented
tutorial report and provenance (engine 1.0.0, codegen 1.0.0).

Replaces or deletes text introduced by (scripts/check_doc_reverts.py's
History.introducer for judged pages; git blame / git log -S at origin/main
for CHANGELOG.md, docker/README.md, tutorial/README.md and code blocks):
- b2a578c (DOCS-ENGINE, #300): CHANGELOG.md, README.md, docker/README.md,
  tutorial/README.md, docs/coverage.md, docs/pine_v6_audit_master.md,
  docs/pine_v6_coverage_detail.md, docs/pages/abi-stability.md,
  configuration.md, examples-multi.md, ffi-python.md, install.md,
  integration-cmake.md, live-surface.md, mtf.md, native-engine.md,
  pine-to-native.md, public-contract.md, report-schema.md, tutorial-macd.md
- 133f571 (#308): README.md (the benchmark "Last refresh" sentence)
- 0d76a09 (Wave G, #289): docs/pages/abi-stability.md (the V19-FIX
  sentence)
- d093560 (INT26, #290): docs/pages/abi-stability.md (the H-THIN sentence,
  the version-macros text), docs/pages/native-engine.md (a line of the 1.0
  C boundary paragraph)
- 2fcbb52 (R5 lane F2): code-block lines in docs/pages/abi-stability.md
  (PINEFORGE_GIT_SHA) and docs/pages/integration-cmake.md (pkg-config
  Version)
- 112c134 (#302): README.md (the scoreboard paragraph, extended only)
- b1fbf0b (detailed Pine v6 coverage report): docs/pine_v6_coverage_detail.md
  (the "(hard reject)" heading and the request.financial bullet)
- e7cdf05 (native execution terms): docs/pages/abi-stability.md (the
  "PF_ABI_VERSION remains 4" clause)
Three rewrites bring back d093560's wording, which b2a578c made "planned
1.0" and which is true again now: README.md's "the 1.0 C surface does not
spell", and docs/pages/native-engine.md's "does not spell in 1.0" and
"Deprecated public spellings, removed for 1.0".

docs/pages/native-engine.md and docs/pages/pine-to-native.md are
ci_docs_only.py PROOF_READS, so this change runs CI's full lanes; no code
block of either page changed.

Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>