INFINBOT — CODE REPAIR AND CURRENT-HOST ACCEPTANCE
2026-10-13 | Software repair package, not production or real-money clearance

WHAT WAS FIXED
* Owner gateway authentication, bounded messages, token revocation checks and truthful command results.
* Unsupported order commands are rejected. A freeze never claims broker liquidation.
* Restart-persistent entry freeze, six-hour countdown and 0.0000 worker allocation.
* Both --file and --filepath work for the JSON auditor. USD must be explicit;
  exact Decimal arithmetic, chronology, duplicate checks and adjustments are retained.
* Trading worker ranking remains distinct from enterprise exception prioritization.
* Eligible scores require matching complete recorded-session metrics. 100 complete
  scheduled sessions, >=97/100 and no hard risk veto remain research conditions only.
* Read-only paper account/position diagnostics; fresh crypto REST and acknowledged
  WebSocket observations; cash/equity and position mismatches remain blocked.
* AES-GCM encrypted SQLite backup plus actual byte recovery and integrity checks.
* Managed Friday/Sunday host jobs preserve other jobs. An archive depends on a
  successful current export audit, not a five-minute scheduling assumption.
* Notifications use InFinBot; API acceptance remains distinct from phone receipt.
* Original ledger names, historical format readers and existing module aliases
  remain compatible. The enterprise stays Foresixa; this product is InFinBot.

YOUR LGC CONTRACT IS NOT INCLUDED, EDITED OR APPROVED BY THIS PACKAGE.
Commercial license controls remain blocked without separately approved current
terms and a trusted tenant/session host. Security tests use synthetic terms only.

WHAT A CONSOLIDATED RUN MEANS
One command reads YOUR installed code, current ledger, actual export and private
paper credentials on YOUR Mac. It runs component checks and saves one private
JSON receipt containing passed, blocked and unverified results. It also writes a
separate zero-entry policy and operational heartbeat records, and makes an encrypted
backup if selected. It does not seed, reset, delete or alter the simulation ledger.
It cannot manufacture missing scheduled sessions, perform a broker liquidation,
grant IRS filing approval, approve the contract or authorize real-money trading.

BEFORE THE HOST RUN
You need the current persistent simulation ledger, actual exported disposition JSON,
your privately rotated paper credentials file, and the exact recorded worker tag.
Do not select a stored test snapshot as current data. Confirmed fixture metadata
blocks current-ledger acceptance. Keep old exposed keys revoked at the broker.
Fresh authentication alone cannot prove their revocation.
Crypto account mode must be PAPER and the broker endpoint paper-api.alpaca.markets.
The separate market-data endpoint is data.alpaca.markets. Never relabel live keys.
No private token, key, password, actual ledger or taxpayer data is packaged here.

INSTALL AND RUN (Python 3.10+; Mac only)
Extract infinbot-release.zip in Downloads. Its folder is infinbot-release.
The installer backs up replaced CODE into your project's private/code-backups folder.
It does not overwrite databases, credentials, LGC contracts or host configuration.
Run this block in Terminal:

cd "$HOME/Downloads/infinbot-release" && python3 install_infinbot.py --target "$HOME/ForesixaQuant" && cd "$HOME/ForesixaQuant" && python3 -m venv .venv-infinbot && .venv-infinbot/bin/python -m pip install -r requirements-infinbot.txt && .venv-infinbot/bin/python infinbot_setup.py && .venv-infinbot/bin/python infinbot_acceptance.py --config private/infinbot-host.json

Finder will ask you to select the three real files. The credentials selection must
be a FILE, not a folder of scripts. Enter the actual worker execution tag when asked.
Setup creates new private operational token/password files locally, never broker
credentials or account funding. Existing files are preserved. Make a separate
private recovery copy of the archive-password file; without it, encrypted archives
are unrecoverable. Keep operational and broker secrets out of git, shared folders
and packages. File permissions are not a substitute for host disk protection.

Re-run current acceptance after setup:
.venv-infinbot/bin/python infinbot_acceptance.py --config private/infinbot-host.json

Receipt path is printed. Receipts may contain private financial observations.
Share only a redacted status/blocker summary; never upload private/ or your ledger.
The receipt directory is private/receipts. No synthetic current observations are used.
Exit 1 means unresolved checks, not a request to seed data until it passes.

CURRENT ADAPTER SCOPE
ledger_reporting.py is a newly developed, read-only adapter for the recovered
accounts/positions/orders/dispositions schema. It is not an invented reconstruction
of a previously tested missing file. Worker trade ranking separately expects joined
form_8949_ledger and simulated_orders with recorded tag/asset attribution.
An incompatible schema blocks; no automatic destructive migration or symbol-based
guess is performed. The current actual export must use explicit currency="USD".

OWNER CONSOLE AND OBSERVERS
After reviewing the host receipt, you may start the private local runtime:
.venv-infinbot/bin/python infinbot_start.py --config private/infinbot-host.json
It starts a loopback owner gateway, a static console and bounded zero-entry ledger
observers. PIDs are recorded, but PIDs alone are not service readiness evidence.
Open http://127.0.0.1:8766/ on that Mac. Privately copy the locally generated token
from private/infinbot-gateway-token.txt into the console; do not send it to chat.
Tokens are never stored by the console. Only read-status and freeze-entry actions
are supported. Existing old services must be stopped by their known owner before
restarting their replacement. Do not broadly kill unrelated processes.
This is a responsive web console, not a native phone application. Remote phone
access requires a reviewed HTTPS/WSS host, valid certificates and authorized origin.
The default loopback listener deliberately does not expose the Mac publicly.
Visual viewport checks were not completed: local browser executable unavailable,
and the cloud browser's generated-page URL policy blocked the preview. Review the
console on the actual browser before a frontend release.

The six-hour observation deadline survives restart. It never auto-extends. After
owner review, renew only the observation window while KEEPING entries frozen:
.venv-infinbot/bin/python infinbot_observer_window.py --config private/infinbot-host.json --review-reference "your recorded review reference"
No route clears the freeze or enables broker execution in this repair release.

SCHEDULES — INSTALL ONLY ON THE INTENDED MAC
.venv-infinbot/bin/python infinbot_schedule.py --config private/infinbot-host.json --install
Friday 23:55: encrypted ledger backup/recovery check.
Sunday 23:50: consolidated acceptance.
Sunday 23:59: archive the actual export after its arithmetic/date validation.
Mac timezone must be America/New_York (or its US/Eastern alias). Readback confirms
installation; a later execution receipt confirms a scheduled run. Cron may miss
runs while the Mac sleeps/offline; there is no catch-up or automatic restart claim.
Unmarked older archiver jobs block installation rather than silently duplicating
or deleting them. Review/remove only the old duplicate job you own, then re-run.
No retention deletion is enabled. Local ciphertext is not an independently verified
offsite copy. Use --backup-dir during setup for your separately protected storage
location; physical independence and offsite recovery still require a real rehearsal.

NOTIFICATION TEST — ONLY WHEN YOU AUTHORIZE A REAL TEST
.venv-infinbot/bin/python infinbot_notify_check.py --config private/infinbot-host.json --credentials /absolute/private/path/notification_credentials.json --send-test
This sends a plainly labelled test through your existing Pushover configuration.
It never says that a crisis or liquidation happened. Confirm YES only if it actually
arrived on your phone. That owner-confirmed receipt is separate from API acceptance.
Network timeout remains unknown; the adapter never blindly resends after ambiguity.

STILL REQUIRES REAL INPUT/VERIFICATION
* Preserve your already configured futures connection. This acceptance checker has
  not inspected that existing connector or observed its current messages, so it
  reports UNVERIFIED rather than UNCONFIGURED or requiring a new provider.
  Existing connector configuration and fresh observations are needed for its host
  review; no replacement provider, credentials or contract order route is created.
* Broker-side revocation evidence for credentials exposed previously, privately loaded
  fresh credentials and current host diagnostics.
* Actual closed dispositions, attribution and complete scheduled-session metrics.
* Actual scheduler execution, independent backup recovery, phone delivery and browser
  review. This package cannot operate your Mac from this chat environment.
* LGC contract and release disposition remain outside this authorized repair.

CME DATAMINE UPDATE — 2026-10-13
The configured provider is CME DataMine. Preserve the existing setup and see
DATAMINE_ACCEPTANCE.txt for the historical API route, supported file schema and
offline acceptance command. No new provider or credentials are generated.
The token audit reads an existing externally managed token from Mac Keychain
or an owner-private file. It does not claim system-wide purge, old-key revocation
or verification that the production signing consumer uses that token.

Verification performed here: isolated software tests and real loopback gateway/
encrypted recovery exercises. These do not establish actual host performance,
live-capital readiness, learning effectiveness, collected revenue or IRS compliance.