[mikomiel]

Purpose

Apply the owner's approved minimal publication setup for the independent Polish adaptation. Refs #29; this PR does not close the issue before acceptance and integration.

Scope

• Credit mikomiel as the adaptation's maintainer, without inventing a company, professional qualification or private contact details.
• Make GitHub Issues the public correction channel; warn against posting health data, passwords, other people's data and documents from individual cases.
• Add one canonical, accessible notice in the existing index.html, linked from the header and README. Retain upstream attribution, licensing, noindex and the existing machine-review warning.
• Describe local search, lack of reader-written search storage, ordinary browser caching, GitHub Pages IP logging and public issue handling with AI assistance. Do not claim that GitHub processes no data or that the publication has undergone a complete legal-compliance assessment.
• Update the old /pulls contact assertion to the approved /issues contact contract; add three metadata contracts and one real-browser scenario.

No advice, chapter registry, reader algorithm, dependencies, publication allowlist, workflow, trigger or permission changed. No consent banner, analytics, account system or issue-submission form was added. Source main remains 20 chapters / 473 reader-eligible records / 68 pending records.

Evidence

• PASS: node --test --test-reporter=tap tests/*.test.mjs — 293/293.
• PASS: node tools/pl/lint.mjs — 541 records, 0 errors, 0 warnings.
• PASS: node node_modules/playwright/cli.js test --project=desktop --project=mobile — 100/100.
• PASS: four real negative controls (wrong maintainer link, wrong correction channel, missing IP disclosure, an actual reader localStorage write). Each failed for the intended reason; files were restored byte-for-byte.
• PASS: git diff --check and unchanged book/, reader.mjs, tools/, .github/ and AGENTS.md against the integration base.
• The three new metadata tests were demonstrated red on the prior HTML/README before the notice was added.
• Local Firefox/WebKit NOT_RUN; the existing CI runs all four projects. CI for the published HEAD must be read separately.

Source assessment and limits

Checked 2026-11-05: the complete short GitHub Pages overview, including Data collection, and the introduction and Personal Data We Collect sections of the GitHub General Privacy Statement. A full privacy statement was fetched, but no complete legal analysis of all its provisions is claimed.

• https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#data-collection
• https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement

The local browser test exercises the built site under its project prefix. After load, search, Enter and reset create no request, cookie or local/session storage write. This is source/build evidence, not a statement that the live hosting platform has no logs or processing.

Integration and publication

Owner review/merge and the existing manually run Pages workflow remain the selected route. This session does not merge the PR, dispatch Pages, alter protections or configure identities. The notice is not live merely because this PR exists or merges. After the owner publishes, verify the served commit and actual notice/content separately. Documentation result: source_docs in the existing HTML/README; no separate KB document or deferred documentation debt.

[mikomiel]

Agent update — Pi. The owner approved crediting mikomiel as the independent Polish adaptation’s maintainer, GitHub Issues for public corrections (no sensitive/private case documents), and no added analytics. PR #39 implements those decisions in the existing reader and README, including local search/storage behavior, GitHub Pages IP logging, public issue handling with AI, and the limits of this factual notice. No company or professional qualification was invented.

HEAD 80a478a9db5a1f23062102566e52bd6072c950e4: local Node293/293, content lint541/0/0, Chromium desktop/mobile100/100, and four intended-failure controls with byte-for-byte restoration PASS. Exact-HEAD GitHub CI5/5 PASS (run42080202495); all four browser projects200/200. An independent automated review was unavailable in this session; no independent reviewer result or legal-compliance assessment is claimed.

Issue remains open for owner acceptance/integration of #39. The notice is not live merely because this PR exists. Owner review/merge and the existing manual Pages workflow remain the selected route; this session has not merged or dispatched Pages. Chapters21–23 are being prepared independently.

[mikomiel]

Agent update — Pi.

Kryteria dotyczące decyzji i informacji źródłowej są spełnione. Właściciel zatwierdził opis roli mikomiel, GitHub Issues jako publiczny kanał korekt bez dokumentów spraw i danych wrażliwych oraz brak dodanej analityki. PR #39 został scalony przez mikomiel 2026-11-05 o 21:07:06Z jako 50ae45704021aae6a5c14fd64bd079da8b695c27.

Pełne drzewo merge odpowiada testowanemu HEAD 80a478a9db5a1f23062102566e52bd6072c950e4: 41e13d9f22b99ef54a029bb0b558333851e6caf5. Kanoniczne index.html#publikacja i README opisują utrzymanie adaptacji, publiczne korekty, pomoc AI, lokalne wyszukiwanie i brak zapisów wyszukiwania przez czytnik, zwykłe cache przeglądarki oraz logowanie adresów IP przez GitHub Pages. Nie twierdzimy, że brak analityki oznacza brak przetwarzania przez hosting.

Aktualny main po właścicielskim merge #40 to 2d281958f719b7ba0b8a0b214608890f130f061e; zachowuje informację z #39. PASS: jego trzy kontrole CI, w tym wszystkie cztery projekty przeglądarek — 208/208, run42112025910. Osobny starszy przebieg main50ae4570 nie zakończył instalacji przeglądarek w limicie; nie przedstawiamy go jako sukcesu i nie ponawiamy nieaktualnego refu.

Zamknięcie dotyczy zatwierdzenia faktów i ich integracji w źródle, nie certyfikacji zgodności prawnej ani wdrożenia. Nie uzyskano niezależnej opinii prawnika lub lekarza. Pages nadal ma ostatni udany run41137960445 na a009dec5; nie wykonano nowego dispatchu ani weryfikacji serwowanej nowej treści. Publikacja pozostaje osobnym krokiem właściciela po integracji pozostałych rozdziałów, a stan strony musi być potem sprawdzony na wdrożonym SHA.