Skip to content

chore: certify foreign change - store/planning docs evidence reconciliation - #33

Merged
lukisch merged 2 commits into
masterfrom
chore/certify-store-docs
Nov 7, 2026
Merged

lukisch merged 2 commits into
masterfrom
chore/certify-store-docs

Conversation

@lukisch

@lukisch lukisch commented Nov 7, 2026 •

Copy link
Copy Markdown
Collaborator

Herkunft

Nachzertifizierung einer fremden, uncommitteten Aenderung im Klon C:\_Local_DEV\repos\ExplorerPro (master 805067f, vier Dokumente, ein Schreibvorgang am 2026-11-01 15:35:17, Urheber nicht belegbar). Commit 1 ist byte-identisch zur fremden Aenderung (+49/-13). Ticket T-20261107-925938302.

Zwei Commits

  1. chore: certify foreign change ... (a6b54f5): die fremde Aenderung unveraendert.
  2. docs: remove agent-internal references from certified store docs (2dcd3dc): entfernt interne Bezuege aus dem Evidenzabsatz ("TASKPLAN #518/#519", "CCC-Pause", "Dokumentationsslice") und korrigiert die Selbstverweisung in STORE_ISSUES.md. Die sachlichen Aussagen bleiben. Grund: Hygiene-PR chore(hygiene): untrack agent-internal TASKPLAN_STATUS_2026-09-17_1324-*.md #2.

Was die Aenderung tut

  • Kennzeichnet die Juli-Planung und die Oktober-Submission-Eintraege in STORE_ISSUES.md, PORTIERUNGSPLAN.md, ROADMAP.md und WINDOWS_STORE_PREP.md als datierte Staende.
  • Ergaenzt einen Evidenzabsatz: in diesem Checkout liegen kein ExplorerPro.msix und keine Abnahme-Receipts, die Hashes sind historisch, WACK ist als uebersprungen dokumentiert, Store-Status und installierte Version wurden nicht neu zurueckgelesen.
  • Loest den Widerspruch "1.0.8 Certification" gegen "1.0.8 Published", indem beide als historische Snapshots benannt werden.

Pruefung

  • Diff vollstaendig gelesen, nur Doku. Die 10 neueren Commits auf origin/master (1b5aaa2) beruehren diese vier Dateien nicht: kein Konflikt, nichts ueberholt.
  • Aussagen gegen origin/master geprueft: releases/windowsstore/ enthaelt nur v1.0.8 und v1.0.9 release-notes.json; store_package.json deklariert 1.0.9.0 und Geiger.ExplorerPro; der Tag v1.0.9 existiert, die GitHub-Releaseliste zeigt nur 1.0.8.
  • Keine Secrets, Kontaktdaten oder neuen IDs in den hinzugefuegten Zeilen; auf allen vom PR hinzugefuegten Zeilen findet grep -Ei "taskplan|ccc|T-20[0-9]{6}-|\.TOPICS|lukas" nichts. tests/test_store_materials.py: 5 passed, 1 skipped, wie auf der Basis.

Hinweise fuer den Review

  • Derselbe Absatz steht weiterhin in allen vier Dateien (bewusst nicht umgebaut).
  • Nicht angefasst, weil schon auf origin/master: ROADMAP.md "TASKPLAN-Abgleich TW-EP-06" und der Maintainer-Name; in STORE_ISSUES.md die Ticketspalte T-20260928-288887892 (auch in CHANGELOG.md und tests/test_store_regressions_20260928.py verwendet).

Nicht mergen; Zweitpruefung durch eine andere Instanz.

🤖 Generated with Claude Code

https://claude.ai/code/session_01THB2EysTVQFXz5moenpBvW

Lukas Geiger and others added 2 commits November 7, 2026 09:26
…iation

Herkunft: uncommitted working-tree change in the clone C:\_Local_DEV\repos\ExplorerPro
(master 805067f), four files written in one operation at 2026-11-01 15:35:17,
author not provable (agent work; the text cites "TASKPLAN #518"). Found during the
licence inventory of T-20261031-411493180, tracked as T-20261107-925938302.
Content is byte-identical to that change (+49/-13); wording is the foreign author's.

What it does: marks the July planning statements and the October submission records
as dated snapshots (STORE_ISSUES headings, PORTIERUNGSPLAN/ROADMAP gate rows,
WINDOWS_STORE_PREP pretest/blocker sections) and adds one evidence paragraph:
no ExplorerPro.msix and no acceptance receipts in this checkout, hashes are historical,
WACK documented as skipped, live Store status and installed version not re-read.

Pruefung (sonnet-worker-s1@ASUS-GEI, 2026-11-07):
- Diff read in full; docs only. The 10 newer origin/master commits (1b5aaa2) do not touch
  these four files, so no conflict and nothing already superseded.
- Claims checked against origin/master: releases/windowsstore has only v1.0.8 and v1.0.9
  release-notes.json (no .msix, no receipts); store_package.json declares 1.0.9.0 and
  Geiger.ExplorerPro; STORE_ISSUES already states "WACK ... uebersprungen". Tag v1.0.9
  exists, the GitHub release list shows only 1.0.8 - the text claims nothing beyond that.
- No secrets, contact data or new IDs in the added lines; renamed headings are not
  referenced by any other file; tests/test_store_materials.py 5 passed, 1 skipped
  (same result as on the unchanged base).
- Not a deterioration: it resolves the contradiction "1.0.8 Certification" vs "1.0.8
  Published" by labelling both as historical snapshots.
- Remark, deliberately left unchanged: the same paragraph is repeated in all four files,
  and it names the internal references "TASKPLAN #518/#519" and "CCC-Pause".

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01THB2EysTVQFXz5moenpBvW
Hygiene-PR #2 already took agent-internal material out of this public repo, so the
certified evidence paragraph must not name internal task numbers or process terms.

Removed: "TASKPLAN #518" (heading, four files), "TASKPLAN #519" and "#519" (now "steht noch
aus"), "CCC-Pause" and "Dokumentationsslice" (now "in dieser Dokumentationsaenderung").
Corrected: in STORE_ISSUES.md the paragraph referred to itself ("`STORE_ISSUES.md` enthaelt
...", now "Dieses Dokument enthaelt ..."). The factual statements are unchanged.

Not touched (pre-existing on origin/master): ROADMAP.md "TASKPLAN-Abgleich TW-EP-06",
the maintainer name in ROADMAP.md, and the ticket column T-20260928-288887892 in
STORE_ISSUES.md (also used in CHANGELOG.md and tests/test_store_regressions_20260928.py).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01THB2EysTVQFXz5moenpBvW
@lukisch
lukisch merged commit 8b10c97 into master Nov 7, 2026
12 checks passed
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