SniperGold_ML/docs/P3_S25_1R_AUTHORITATIVE_WORKSPACE_RESTORATION.md

217 lines
8.9 KiB
Markdown

# P3-S25.1.R — AUTHORITATIVE WORKSPACE RESTORATION & CHECKPOINT VERIFICATION
```text
Date : 2026-08-26
Session : P3-S25.1.R — AUTHORITATIVE WORKSPACE RESTORATION
Status : COMPLETE
Result : AUTHORITATIVE WORKSPACE RESTORED AND VERIFIED (Git-clean,
internally coherent, == origin/main)
Answer to the FINAL QUESTION : YES
```
---
## A. Wrong workspace discovered
The previously inspected workspace
```text
D:\TradingTerminal\HFM Metatrader 5\MQL5
```
is **confirmed NON-AUTHORITATIVE** (Git evidence, not just path name):
```text
remote origin = https://forge.mql5.io/chiki2bum2/mql5.git (NOT SniperGold_ML.git)
branch main
HEAD 609bcfd077d13a82260367f35613d9ef42c69b29
tracked 1 file
status 12 changed entries
untracked 205,241 files (the free-floating MQL5 tree: Experts/Files/Include/
Indicators/Scripts/Shared Projects, none of it tracked by this repo)
```
It is the live MetaTrader `MQL5` skeleton owned by the account-`mql5.git`
remote. Its 200k+ loose files are NOT part of any SniperGold commit. This
workspace was preserved exactly as found — NOT added, merged, copied, committed,
reset, or deleted (per section 5 of the task).
---
## B. Candidate workspaces inspected
| # | Path | Git? | remote | branch | HEAD | working tree | tracked | latest SniperGold commit | Status |
|---|------|------|--------|--------|------|--------------|---------|--------------------------|--------|
| 1 | `MQL5` terminal root (`D:\TradingTerminal\HFM Metatrader 5\MQL5`) | yes | `mql5.git` | main | `609bcfd` | dirty (12 chg, 205k untracked) | 1 | none | NON-AUTHORITATIVE (wrong repo) |
| 2 | `Shared Projects\SniperGold_ML_authoritative` | yes | **`SniperGold_ML.git`** | main | **`8d631ed`** (= origin/main = remote) | CLEAN | 454 | **`8d631ed` (P3-S25.1)** | **AUTHORITATIVE** |
| 3 | `Shared Projects\SG_WS` | yes | `SniperGold_ML.git` | main | `ed01af2` (stale, origin/main ref stale) | CLEAN | 206 | `ed01af2` (P3-S17) | STALE clone; fails crit.; NOT authoritative |
| 4 | `Shared Projects\AlgoForge\publish\AlgoForge` | yes | `SniperGold_ML.git` | main | `1c0da62` (P3-S13 era) | — | — | `1c0da62` | MetaQuotes publish copy; STALE; NOT authoritative |
| 5 | `Shared Projects\SniperGold_ML` | no git | n/a | n/a | n/a | n/a | n/a | n/a | loose plain folder; not a clone |
| 6 | `Shared Projects\SniperGold_M_authoritative` | no git | n/a | n/a | n/a | n/a | n/a | n/a | loose `ml` folder only; not a clone |
| 7 | `Shared Projects\SniperFold\SniperGold_ML_authoritative` | no git | n/a | n/a | n/a | n/a | n/a | n/a | not a clone |
A recursive search of the terminal tree found exactly four `.git` dirs (#1#4). No
SniperGold clone exists under `Terminal\Common`. No clone was modified during
discovery.
Note: the searched directory names under `D:\TradingTerminal\...\MQL5\Shared
Projects\SniperGold_ML_authoritative` (shown in the folder listing) are the
same repo's own content; the three loose `SniperGold*` directories are not git
repositories.
---
## C. Authoritative repository selected
```text
D:\TradingTerminal\HFM Metatrader 5\MQL5\Shared Projects\SniperGold_ML_authoritative
```
Selected by satisfying ALL nine authoritative criteria, not by path name:
1. origin remote == `forge.mql5.io/chiki2bum2/SniperGold_ML.git`
2. branch == `main`
3. local HEAD == origin/main == remote HEAD == `8d631ed...`
4. working tree CLEAN ✓
5. P3-S25 / P3-S25.1 history present ✓
6. latest authoritative handover present and tracked ✓
7. expected P3 history (S1 … S25.1) present ✓
8. contains `ml/p3/`, `docs/`, previous P3-S25.1 research namespace ✓
9. no unexpected untracked project-wide files ✓
The Git ancestry of `HEAD == 8d631ed` (the P3-S25.1 recovery #3 commit)
matches the latest authoritative handover, which the stale `SG_WS` clone does
not carry.
---
## D. Origin URL
`https://forge.mql5.io/chiki2bum2/SniperGold_ML.git` (fetch & push)
## E. Correct branch
`main`
## F. Correct HEAD
```text
8d631ed58d1bb86d02513b295a72a9c352ddb4be
```
(== `origin/main` == `origin/HEAD` == remote `HEAD`)
## G. Latest handover found
```text
docs/SESSION_HANDOVER_2026-08-26_P3_S25_1_EXTERNAL_TICK_INGESTION.md
(P3-S25.1 RECOVERY #3 — Stage A complete, Stage B NOT STARTED;
classification E — environment/execution limitation)
preceding: docs/SESSION_HANDOVER_2026-08-26_P3_S25_EXTERNAL_DATA_BASIS_VALIDATION.md
```
Read completely (both handovers) plus the governing
`docs/CODE_VERIFICATION_AND_SILENT_BUG_POLICY_v1.md`, per handover-first.
## H. P3 history continuity
The corrected, internally coherent `git log` chain runs from the AlgoForge/
source-of-truth lineage through P3-S17.x, then:
```text
P3-S18 → S19 → S20 → S21 → S21.R → S22 → S22.1 → S22.2 → S22.3 → S22.4
→ S23 → S24 → S25 → S25.1
```
114 commits total; every required phase is represented by real commits with
real SHAs taken from Git (no invented history).
## I. Role of the referenced checkpoint `8d631ed…`
```text
git cat-file -t 8d631ed58d1b…4be -> commit
git show --no-patch --decorate --oneline 8d631ed…
-> 8d631ed (HEAD -> main, origin/HEAD, origin/main) docs+research: …
S25.1 P3 recovery #3 interruption diagnosis … + session handover
```
CONCLUSION: `8d631ed58…b4be` **IS the current authoritative HEAD**, equal to
`origin/main`, `origin/HEAD`, and the remote `HEAD`. It is NOT an earlier
ancestor and it is NOT superseded — it IS the latest authoritative checkpoint
for P3-S25.1 Stage A completion. No forced checkout was performed and no SHA
was changed; the working tree was already at it.
## J. Working tree status
```text
git rev-parse HEAD : 8d631ed58d1bb86d02513b295a72a9c352ddb4be
git ls-remote origin HEAD : 8d631ed58d1bb86d02513b295a72a9c352ddb4be HEAD
git branch --show-current : main
git status --short : (empty — CLEAN)
git stash list : (empty — no stash)
git remote -v : origin = https://forge.mql5.io/chiki2bum2/SniperGold_ML.git
```
Required state **CLEAN**; no untracked files; `local HEAD == origin/main`.
## K. Source data location
The research repository does NOT ship the 34.5 GB CSV. The external source
lives in the terminal **Files** area:
```text
MQL5\Files\XAUUSD_mt5_ticks.csv
exists : YES
size : 34,473,661,010 bytes (34.5 GB)
mtime : 2026-08-24 22:44:41 UTC (unchanged vs. handover record)
sha256 : 5252ce8f5b0e7d286b71a3172c7ef9c1009c8e4b1254ac67400a803fcd85cba1
(already documented in the P3-S25.1 handover; NOT re-hashed —
no source-integrity contradiction)
```
Source is unmodified. **No ingest was performed** (a full SHA pass is not
required and was not re-run to resolve any contradiction).
## L. P3-S25.1 ingestion code availability
Namespace `ml/p3/p3_s251_external_ingest/` is present and **tracked**:
```text
s251_ingest.py, s251_parse.py, s251_aggregate.py, s251_checkpoint.py,
s251_oracle.py, s251_config.py, s251_subset.py, s251_tests.py, fixtures.py,
output/{p3_s251_checkpoint.json, p3_s251_diagnosis_evidence.json,
p3_s251_tests.json}, scratch/mt100.csv (fixture)
```
Contains: bounded-memory streaming ✓, chunk manager ✓, checkpoint ✓, resume
(T10/T11/T12 PASS) ✓, chunk hashing ✓, M15 aggregation ✓, M30 aggregation ✓,
oracle (independent, T05/T07 equality PASS) ✓, tests ✓, recovery logic ✓.
Real 34.5 GB ingest NOT executed. The only checkpoint is a test-fixture artifact
(`run_id "src_clean"` over `scratch/mt100.csv`, 2 chunks); no valid real-source
checkpoint exists.
## M. Confirmation that NO ingestion occurred
The 34.5 GB real source was never processed. Observed rows of any "ingest"
are `row` for the 40-row fixture (chunks 0..1 of 2 for the fixture). No chunk
of the real source was started or processed (`Chunk processing: 0`).
## N. Confirmation that NO production source changed
- `MQL5\Files\XAUUSD_mt5_ticks.csv` not modified (size/mtime identical to the
documented record; only the previously-measured sha256 was re-quoted).
- No production MQL5 file in this repository was edited (repo `git status`
clean before AND after this session).
- The internal single-tracked repo (`origin/` != SniperGold) was left untouched.
## O. Next allowed action
```text
P3-S25.1 Stage-B real-source checkpoint initialization
```
Resume is permitted ONLY under the handoff's resume preconditions:
(1) a valid real-source checkpoint (source SHA/size/mtime reconcile) AND
(2) execution in bounded **one-chunk / small-bound-batch** units with per-chunk
checkpoint + recovery log, returning control to the assistant frequently.
Start with exactly ONE real-source chunk. No monolithic full-file ingest.
---
*End of P3-S25.1.R authoritative workspace restoration report.*