Repository navigation
docs: align public technical reference to v4.0.0 - #3
Merged
Merged
Conversation
FaresDisusa
marked this pull request as ready for review
August 31, 2026 15:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Align the unreleased public v4.0.0 candidate with the current private truth
without publishing proprietary or personal context.
What changed
administrative coordination, explicitly non-technical.
trading runtime, order placement, account operation, or capital connection.
private label, SHA, manifest, instrument contract, or performance data.
plus DSR on the current synthetic route; CPCV/PBO only as programme methods
where applicable.
engine coverage or current trading activity.
Unreleased, changed the date field tolast_verified: 2026-09-01, and removed any premature release date.Africa/Tuniscivil date to avoid a UTC-midnight false positive in CI.repository while retaining factual maintainer checks and required CI.
Validation completed locally on
e194390git diff --checkfinding
Final-head GitHub gates
Release boundary
Once final-head CI passes, this PR is ready for the maintainer's merge decision.
Merging it does not by itself create
v4.0.0or publish a GitHub Release.At the actual release, replace
unreleasedwith the published state, add thereal squash-merge/tag date, and rerun all checks on that final head. Any
post-release correction must use a later patch version.
Explicitly out of scope
This change does not modify the private trading implementation,
disuza.com,/guest,llms.txt,llms-full.txt, the organization-level.githubrepository, LinkedIn, Wikidata, or external SEO metadata. It publishes no age,
student status, education, health/ADHD context, family financing, private
strategy detail, infrastructure coordinate, credential, or unpublished result.