tradingcodex 1.0.1__tar.gz → 1.1.0__tar.gz

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/CHANGELOG.md

@@ -2,6 +2,62 @@
 
 ## Unreleased
 
+## 1.1.0 - 2026-07-16
+
+- Make managed skill invocation resilient without weakening authority: Build,
+  Brain, Strategy, and native order entrypoints now share one lexical parser
+  that accepts the first meaningful line, matching projected-skill Markdown
+  links, same-line requests, BOMs, and cross-platform newline forms. Prompt
+  proofs remain bound to the original bytes, and order flags, approvals,
+  confirmations, one-effect limits, and replay protection remain strict.
+- Give `trading-build` credential-free, limited public HTTP(S) and HTTPS Git
+  retrieval while keeping root native web search disabled. Public source files
+  are staged only below the workspace-specific cache-backed scratch provider
+  directory, remain inert, and may be hashed, diffed, inspected, or
+  syntax-checked but not installed or executed. The proxy uses full HTTP
+  transport only for Git Smart HTTP's read-only protocol POST; ordinary HTTP
+  remains GET/HEAD-only and general POST stays blocked. Authentication,
+  model-authored request bodies, private/local targets, shell pipelines,
+  dependency installation, direct `trading/` downloads, Git publication, and
+  broker effects remain blocked.
+- Make the active Build-turn shell a narrow, non-extensible review lane. Edits
+  use `apply_patch`; admitted commands are public GET/HEAD, enumerated read-only
+  HTTPS Git, limited workspace reads, inert provider hash/diff/Git inspection,
+  exact isolated `py_compile`, and allowlisted workspace-launcher operations.
+  General interpreters, helper scripts, test runners, build systems, shell
+  composition, model-authored POST, and native browser/web/network tools now
+  fail closed during Build while Research browser behavior remains unchanged.
+- Add provider source provenance, full bundle hashing, secret/VCS/symlink
+  rejection, immutable approval snapshots, and provider-first connector
+  onboarding. Build-side inspection can return an inert bundle-only hash and
+  `service_check_required` posture without reading the central ledger; only the
+  interactive operator path resolves canonical approval state. Missing-provider
+  connection requests no longer leave dead-end connector scaffolds; explicit
+  scaffold-only requests remain available.
+- Preserve the v1 update contract for existing workspaces. `tcx update`
+  refreshes the generated invocation, permission, hook, and skill surfaces
+  without a database migration, keeps workspace identity and user-owned
+  artifacts, and retains the existing explicit home, database, and service
+  address. Fully restart Codex and open a new task after updating so an older
+  task cannot retain its prior hook snapshot. Existing manual provider bundles
+  may omit provenance, while changed or newly unsafe bundles must be reviewed
+  and approved again.
+
+## 1.0.2 - 2026-07-15
+
+- Preserve an attached release workspace's explicit `TRADINGCODEX_HOME`,
+  explicit database override, and projected service address when an update is
+  launched through `uvx` instead of the generated wrapper. This prevents a
+  custom or isolated v1.0.0 workspace from silently switching to the platform
+  default ledger during a package refresh.
+- Fix the public guide's full-width desktop grid so viewport gutters no longer
+  collapse the reading column, and align the provider-to-order header with the
+  primary Guide/Reference/GitHub navigation. Add route, fragment, mobile-menu,
+  and desktop-layout contract tests.
+- Reduce hosted automation usage: normal CI, GitHub Pages deployment, and
+  release verification now use one job each; PyPI publication adds only its
+  protected upload job. Guide-only pushes skip the source CI workflow.
+
 ## 1.0.1 - 2026-07-15
 
 - Add the shared `tcx-artifact` skill to all nine producing fixed roles so

{tradingcodex-1.0.1/tradingcodex.egg-info → tradingcodex-1.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tradingcodex
-Version: 1.0.1
+Version: 1.1.0
 Summary: Local-first investment operating system for Codex-native research and service-gated execution.
 Author: TradingCodex Authors
 License-Expression: Apache-2.0

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/docs/README.md

@@ -47,7 +47,7 @@ If these layers disagree, treat `docs/` as the durable product intent and fix th
 
 | Document | Purpose |
 | --- | --- |
-| [release-readiness.md](./release-readiness.md) | v1.0.1 source readiness, final-commit and exact-artifact validation, and pending tag, publication, and post-publish gates. |
+| [release-readiness.md](./release-readiness.md) | Current v1 release readiness, prior-version update compatibility, exact-artifact validation, and tag, publication, and post-publish gates. |
 
 ## Workflow And Agent Documents
 

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/docs/core-concepts-and-rules.md

@@ -122,7 +122,7 @@ exact root native action -> deterministic hook parse -> native-user permission
   -> policy -> payload validation -> approval/duplicate-request check
   -> mandatory intent audit -> connection -> finalized/uncertain audit
 
-exact first-line $tcx-order-allow -> workspace/session/turn/prompt/mode grant
+exact first-meaningful-line $tcx-order-allow -> workspace/session/turn/prompt/mode grant
   -> protected use_order_turn_grant + PreToolUse proof -> consume once
   -> the same canonical policy/approval/idempotency/live/audit gates
 ```
@@ -131,8 +131,10 @@ The root `tcx-order-submit` and `tcx-order-cancel` skill bundles
 carry no tools. Their complete exact prompt grammar is intercepted by
 `UserPromptSubmit` and dispatched in-process to the service gateway before any
 model runs. The separate `tcx-order-allow` bundle documents current-turn admission:
-an exact physical first line issues one `OrderTurnGrant`, and only root Head
+an exact first meaningful line issues one `OrderTurnGrant`, and only root Head
 Manager can select one later submit or cancel through `use_order_turn_grant`.
+The leading skill may be a plain token or its matching projected Markdown link;
+the order mode and immediate action grammars remain literal.
 `PreToolUse` injects proof that model input and direct MCP callers cannot supply.
 The browser viewer has no mutation route. Fixed roles, public REST, generic
 CLI, and unproven direct MCP calls cannot invoke the final mutation.

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/docs/decision-memory.md

@@ -355,8 +355,8 @@ Memory remains independent of the Brain that produced a decision:
   provenance.
 
 Learning from memory into a Brain is a separate user-controlled curation path.
-Writing requires a root native Codex prompt whose exact physical first line is
-`$tcx-brain`, an explicit source-authoring request below it, an
+Writing requires a root native Codex prompt whose first meaningful invocation
+is `$tcx-brain`, an explicit source-authoring request on that line or below it, an
 actual Codex sandbox that permits the required workspace-local writes, exact
 user-selected source episodes, and counterexamples. The Brain-scoped grant is
 bound to that turn, cannot authorize Build or Strategy work, and does not carry

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/docs/deployment.md

@@ -109,8 +109,12 @@ files are never replaced.
 
 ## Maintainer Prerequisites
 
-Release verification uses Python 3.11 and Node 22, while CI keeps the supported
-Python 3.11, 3.12, 3.13, and 3.14 range green. Node is a maintainer-only build
+Release verification uses Python 3.11 and Node 22. The hosted CI budget runs
+the complete source, frontend, and package gates once on Python 3.11 instead
+of multiplying every push across the supported Python range and native
+platforms. Maintainers run additional supported-version or native-platform
+checks locally or through an explicit temporary/manual workflow when a change
+touches compatibility-sensitive code. Node is a maintainer-only build
 dependency.
 
 Configure PyPI Trusted Publishing for:
@@ -146,12 +150,20 @@ find . -maxdepth 1 -name '*.egg-info' -type d -exec rm -rf {} +
 python3.11 -m build
 python3.11 -m twine check dist/*
 python3.11 tests/platform_wheel_smoke.py --wheel-dir dist
+python3.11 tests/release_upgrade_smoke.py --wheel-dir dist --from-version 1.0.2
 ```
 
 The wheel smoke installs only the built wheel into a clean virtual environment,
 checks distribution metadata against the runtime version, attaches a workspace,
 validates native launchers and generated configuration, runs hooks and MCP
 stdio, exercises the local service, and loads the packaged SPA and assets.
+The release-upgrade smoke starts from the published `1.0.2` package, updates
+that attached workspace with the built candidate wheel, and verifies preserved
+workspace and runtime identity, user-owned state, and explicit home, DB, and
+service-address settings alongside the refreshed generated contract. It also
+preserves the exact provider approval identity and timestamp, compares every
+byte in the immutable provider snapshot, and proves that the candidate runtime
+loads that approved snapshot after the update.
 
 Harness, role, prompt, skill, hook, policy, MCP, or generated-template changes
 also require the disposable-workspace and Codex-native checks documented in
@@ -159,9 +171,12 @@ also require the disposable-workspace and Codex-native checks documented in
 
 ## CI And Release Automation
 
-`.github/workflows/ci.yml` is test-only. It runs frontend verification, safety
-invariants, the supported Python matrix, clean package construction, and native
-macOS and Windows wheel smokes. It never publishes.
+`.github/workflows/ci.yml` is test-only. One Ubuntu/Python 3.11 job runs the
+frontend build, complete Python suite and framework gates, clean package
+construction, the wheel smoke, and the prior-release update smoke. Guide-only
+pushes skip this workflow because
+the Pages workflow validates and deploys only static guide files. CI never
+publishes.
 
 `.github/workflows/release.yml` is manual-only. Every run requires an explicit
 `release_version`. A dry run may build from any selected ref with
@@ -173,12 +188,15 @@ macOS and Windows wheel smokes. It never publishes.
 - the workflow ref is exactly `refs/tags/v<release_version>`
 - the tagged commit is on `origin/main`
 - the wheel and source-distribution filenames carry the same version
-- the built wheel passes the Ubuntu smoke
-- the exact uploaded artifact passes native macOS and Windows smokes
+- `dist/` contains exactly that one wheel and one source distribution
+- the built wheel passes the Ubuntu wheel and prior-release update smokes
 - the protected `pypi` environment approves Trusted Publishing
 
-The same uploaded artifact is downloaded by both native jobs and the PyPI
-publisher. No job rebuilds the distribution after verification.
+The release workflow has one build/verification job. When publication is
+requested, one protected PyPI job downloads that exact artifact and uploads it;
+no job rebuilds the distribution after verification. Native macOS and Windows
+release smokes are local or explicitly scheduled maintainer gates rather than
+automatic jobs on every release.
 
 ## User Guide Pages
 
@@ -189,10 +207,10 @@ prompts, workspace viewing, reusable skills, and everyday recovery. The detailed
 product rules remain canonical in `README.md`, `installation.md`, and `docs/`;
 the guide links back to those sources rather than replacing them.
 
-`.github/workflows/deploy-user-guide.yml` uploads only `guidebook/` and deploys
-it to GitHub Pages after a push to `main` that changes the guide or its workflow.
-It can also be run manually. It does not build or deploy the Python package,
-the Django service, or a production Node runtime.
+`.github/workflows/deploy-user-guide.yml` uses one job to configure, upload,
+and deploy only `guidebook/` to GitHub Pages after a push to `main` that changes
+the guide or its workflow. It can also be run manually. It does not build or
+deploy the Python package, the Django service, or a production Node runtime.
 
 GitHub Pages is configured to use **GitHub Actions** as its publishing source.
 The guide for this repository is published at
@@ -214,8 +232,9 @@ The guide for this repository is published at
    ```
 
 5. In GitHub Actions, run `Manual Release` from that tag with the exact
-   `release_version`. Use `publish_pypi=false` for a rehearsal and
-   `publish_pypi=true` only for the approved publication.
+   `release_version`. Use `publish_pypi=true` for an approved publication; use
+   the optional `publish_pypi=false` rehearsal when release risk warrants an
+   additional hosted build.
 
 Pushing a branch or tag does not publish by itself.
 
@@ -252,7 +271,7 @@ sh "$SOURCE_ROOT/install.sh" \
 On native Windows PowerShell:
 
 ```powershell
-$ReleaseVersion = "1.0.1"
+$ReleaseVersion = "1.1.0"
 $Workspace = Join-Path $env:TEMP "tcx-pypi-$ReleaseVersion"
 New-Item -ItemType Directory -Force $Workspace | Out-Null
 Set-Location $Workspace

{tradingcodex-1.0.1 → tradingcodex-1.1.0}/docs/execution-without-subagent-plan.md

@@ -26,7 +26,7 @@ design, migration, and validation evidence.
   author every class of Codex app Scheduled Task, from simple research and
   monitoring through optional turn-authorized execution.
 - [x] Issue a workspace-, session-, turn-, prompt-, and mode-bound single-use
-  grant only for an exact physical first line `$tcx-order-allow --mode
+  grant only for an exact first meaningful line `$tcx-order-allow --mode
   paper|validation|live`; revoke it after one submit or cancel, after one hour,
   on `Stop`, or when the next user turn starts.
 - [x] Protect `use_order_turn_grant` so only root Head Manager can select the
@@ -82,9 +82,9 @@ Remove `execution-operator` from the fixed-role roster. Native Codex keeps the
 exact immediate submit/cancel path for already-known canonical identifiers and
 adds a separate single-turn path for workflows that create the ticket or
 approval during the turn. The immediate path executes in `UserPromptSubmit`
-before Head Manager runs. The turn path begins only when the physical first
-line is exact `$tcx-order-allow --mode paper|validation|live`, then continues the
-normal workflow with a single-use service grant.
+before Head Manager runs. The turn path begins only when the first meaningful
+line is exactly `$tcx-order-allow --mode paper|validation|live`, then continues
+the normal workflow with a single-use service grant.
 
 `tcx-automate` authors Codex app Scheduled Tasks; it is not a scheduler or
 the skill invoked recursively by each run. Research, monitoring, recurring
@@ -109,7 +109,7 @@ UserPromptSubmit  -> deterministic parse and native-user mandate
 Django service    -> authorize, reserve, audit, invoke adapter, finalize
 Head Manager      -> summarize the already-recorded result; no action authority
 
-native/scheduled user -> exact physical first-line $tcx-order-allow mode
+native/scheduled user -> exact first-meaningful-line $tcx-order-allow mode
 UserPromptSubmit      -> bind one grant to workspace + session + turn + prompt + mode
 roles/services        -> create and approve canonical ticket state
 Head Manager          -> call protected use_order_turn_grant once
@@ -152,7 +152,8 @@ Each bundle follows the normal TradingCodex skill shape, including `SKILL.md`
 and `agents/openai.yaml`, but contains no tool authority. The skill documents an
 action syntax intercepted by the hook before the model runs.
 
-The complete trimmed user prompt must have one of these forms:
+The complete meaningful user prompt must have one of these canonical plain
+forms:
 
 ```text
 $tcx-order-submit --ticket-id <ticket-id> --approval-receipt-id <receipt-id>
@@ -162,10 +163,13 @@ $tcx-order-cancel --ticket-id <ticket-id> --broker-order-id <broker-order-id> --
 $tcx-order-cancel --ticket-id <ticket-id> --broker-order-id <broker-order-id> --approval-receipt-id <receipt-id> --live-confirmation <token>
 ```
 
-Parsing rules are intentionally strict:
+Parsing rules are intentionally strict. One UTF-8 BOM, normalized CRLF/CR/NEL/
+Unicode line separators, leading/trailing blank lines, and a Markdown link whose
+label and target match the projected workspace action skill are presentation
+variants only:
 
 - Parse with `shlex.split`; never use a shell or evaluate prompt content.
-- Require the skill token to be the first token and the entire prompt to be the
+- Require the skill invocation to be first and the entire meaningful prompt to be the
   action. Free-form prefixes, suffixes, comments, quotations, or a second skill
   invocation are invalid.
 - Accept only the documented `--name value` form. Reject `--name=value`, unknown
@@ -191,8 +195,8 @@ must not fall through to Head Manager as ordinary analysis.
 
 ## Turn-Scoped Order Allow Contract
 
-For a workflow that may create its final identifiers during the turn, the
-physical first line must be exactly one of:
+For a workflow that may create its final identifiers during the turn, the first
+meaningful line must be exactly one of:
 
 ```text
 $tcx-order-allow --mode paper
@@ -200,9 +204,10 @@ $tcx-order-allow --mode validation
 $tcx-order-allow --mode live
 ```
 
-The rest of the prompt is the ordinary interactive or Codex app Scheduled Task
-request. The line accepts no aliases, comments, quotes, extra flags, embedded
-prose, or `--mode=value` form. A free-form mention or later-line occurrence
+The skill token may be its matching projected Markdown link. The rest of the
+prompt is a non-empty ordinary interactive or Codex app Scheduled Task request.
+The line accepts no aliases, comments, quotes, extra flags, embedded prose, or
+`--mode=value` form. A free-form mention or later-meaningful-line occurrence
 does not grant authority. Scheduled and interactive turns use the same parser;
 there is no Automation-origin branch.
 
@@ -264,7 +269,7 @@ normal analysis context:
 The existing provider-call idempotency remains the replay defense if the hook
 event is delivered more than once.
 
-For `$tcx-order-allow`, `UserPromptSubmit` instead validates the exact first line,
+For `$tcx-order-allow`, `UserPromptSubmit` instead validates the exact first meaningful line,
 requires root native `session_id` and `turn_id`, revokes the session's older
 grant, issues the new bounded grant, and continues normal analysis allocation.
 The additional context contains only mode, expiry, single-use posture, and the
@@ -400,8 +405,9 @@ map, or safety routing would otherwise become misleading.
 - Prove that unavailable hook audit blocks before reservation/provider use.
 - Prove that hook result projection contains no raw prompt, reasoning, secrets,
   credentials, raw provider payload, or unallowlisted error text.
-- Accept only the three exact physical-first-line `$tcx-order-allow` modes; reject
-  later-line, malformed, subagent, Workbench, missing-session, and missing-turn
+- Accept only the three exact first-meaningful-line `$tcx-order-allow` modes;
+  reject later-meaningful-line, malformed, subagent, Workbench,
+  missing-session, and missing-turn
   forms without issuing a grant.
 - Prove grant binding to workspace, session, turn, prompt hash, mode, and
   tool-use id; prove one-hour, `Stop`, next-turn, and consumption revocation.
@@ -465,7 +471,7 @@ The change is complete only when all of the following are true:
 8. Generated workspace update safely retires unmodified agent files and
    preserves modified-file conflict protection.
 9. A saved Scheduled Task prompt is processed as an ordinary root turn on each
-   run; only an exact `$tcx-order-allow` physical first line can create one bounded
+   run; only an exact `$tcx-order-allow` first meaningful line can create one bounded
    effect grant, and no Automation-origin detector is involved.
 
 ## Explicit Non-Goals