Skip to content

Use the shared PineForge favicon in API docs - #355

Merged
luisleo526 merged 1 commit into
mainfrom
px/brand-favicon-cdocs-20261008
Oct 13, 2026
Merged

luisleo526 merged 1 commit into
mainfrom
px/brand-favicon-cdocs-20261008

Conversation

@luisleo526

Copy link
Copy Markdown
Collaborator

Uses the shared PineForge favicon in the C API documentation by adding the canonical icon and selecting it with Doxygen’s PROJECT_ICON setting.

The two-file patch is byte-identical to the independently reviewed change after rebasing onto current engine main. The icon matches the canonical 718-byte asset. Docs-only verification, generated-output checks and the complete CI rollup are pending; no parity sweep is needed.

@luisleo526
luisleo526 force-pushed the px/brand-favicon-cdocs-20261008 branch from 9cb5f18 to 9e4433b Compare October 13, 2026 03:14
@luisleo526
luisleo526 merged commit 2ea42e8 into main Oct 13, 2026
13 checks passed
luisleo526 added a commit that referenced this pull request Oct 14, 2026
* docs: the 1.6.0-rc.1 changelog entry

The changelog section for the first candidate of 1.6.0, tag v1.6.0-rc.1 on
commit 04607c1: the selected-window contract
revision 1.3 and the typed failures behind it (#388), finite trade and summary
doubles in every report writer (#384, #388), the favicon of the API
documentation (#355), the removed CI time limits and command-line options (#378),
and the tests, CI and benchmarks changes since 1.5.0 (#375, #376, #377, #382,
#383, #385, #386, #387).

The entry is inserted above the 1.5.0 section; no existing line changes. The
date is the UTC date of the tag.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* README: link the apex pineforge.dev, not the www host

The README header link pointed at https://www.pineforge.dev. The product site
lives at the apex, https://pineforge.dev; the www host is being redirected to
it, and search indexes both forms today. One link changed, nothing else.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

* CHANGELOG: add the selected-window mode and typed failures to the 1.5.0 notes

Two things that are in the v1.5.0 tag were missing from its notes: the opt-in
selected-window mode with retained pre-roll bars (#363, already in
v1.5.0-rc.1) and the typed failures that docker/run_json.py raises for
exceptions from the selected-window helper modules (_typed_failure).

The new subsection "Additions to the 1.5.0 notes" only states what the code
and the #363 text say, with the same "development-only parity candidate"
limits (contract revision 1.3-parity, no claim of complete value-ownership
coverage, cannot be promoted to stable). It adds lines and changes none.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

---------

Co-authored-by: Claude Sonnet 5.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant